-
Notifications
You must be signed in to change notification settings - Fork 293
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] D1 Support #221
Comments
I would also be interested in this. I'm also aware that the current state of D1 is in private beta so it may not be doable at the moment. So I am curious if it is possible to have a worker using both Rust and Typescript in the meanwhile? Where the D1 code is located in Typescript and the main worker code in Rust. |
It is possible, but it's a bit messy. You can use wasm-bindgen snippets generated from TypeScript and then call it from your Rust or you avoid using Until then, D1 support is probably off the table for now. |
Yeah this sounds like a good idea, some sort of unstable branch for non-GA features. I was also thinking of an alternative solution. Having two separate workers, one in Rust and one "normal" in Typescript and connecting them via a service binding. This would mean having to transfer stuff between them though. |
it is now open alpha ╰(°▽°)╯ |
So do we have an status update on this? |
I can't enable d1 feature but I have seen this commit that not released in 0.0.17. Any updates? |
It's been released as of 0.0.18: worker = {version = "0.0.18", features = ["d1"] } |
Is there an existing issue for this?
Description
It would be great if workers-rs had the functionality of wrangler@d1. Although I understand that it may not be the best time to do this as D1 is still in private beta, but it would be cool if the D1 integration was ready to go by the time D1 is public!
The text was updated successfully, but these errors were encountered: