-
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
feat: Added D1 Support #270
Conversation
After some messing about in both |
There's actually still a couple of things I need to add - I'll get these in hopefully in the next couple of days. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks really good, but we need to get some testing in worker-sandbox.
Apologies for the above, Github is funky... |
Apologies for the delay, it's been a crazy couple of weeks. I'm currently writing some tests for this integration using the worker-sandbox crate. Hopefully this PR will be ready for review in the next couple of days. 🙏 cc @zebp |
Hey @logankeenan, Hmm interesting - I had hopefully gotten rid of any problems related to errors at this point. I will spend some time coming up with an interface that allows us to extract the cause of the error. Unfortunately (at the moment) Wrangler wraps the error cause up into the |
@logankeenan interestingly, I had to fix some issues with the macro after @zebp's changes to naming of the D1 interface. Macros are powerful, but can be quite fiddly when it comes to refactoring! I've pushed it up to CF to test and it seems to work okay, but I'm yet to test it locally. Would you mind giving this a go with the fixes and report back? :) |
@FlareLine - My repo is now working as expected. However, I'm embarrassed to say it's because I'm now passing the |
I've tested this branch quite a bit through a demo application. Is there anything I can help with on this PR? |
Hey @logankeenan, I believe there were some conversations happening between @zebp and the D1 team regarding some questions. I'm not sure where those conversations are at. I'd be more than happy if you wanted to contribute some more tests to the PR - I've unfortunately come down with something so haven't had time to come back to this. Apologies for the late reply. |
I can give the PR a look and see where more tests could be added. Take it easy and I hope you get better soon! |
|
Why was this PR closed? |
Uhh no idea, must have fumbled the bag and clicked close with comment - reopened, my apologies! 😅 |
hi guys, thanks for creating this PR, but any updates on it? I think all the issues have been resolved. |
I forked this branch and created a new PR since the original author is unavailable. |
Hey there! I've been attempting to see if I can get a hold of @zebp as there were some conversations he was having with the D1 team. I'm not entirely sure where those conversations are at. I think at the moment it's been fairly busy at Cloudflare, which is probably why it's been difficult to get time to take a look at getting this across the line. |
👋 Good to hear from you. Thanks for the update. Let me know how you'd like me to proceed. I'd be happy to close the PR I just opened. Whatever is easiest. |
@logankeenan I've just cherry-picked your integration test commit into this PR! Appreciate the work! |
Closing in favor of #337 |
Summary
These changes add D1 support to the
worker
crate, resolving #221.Due to the nature of local development with Rust workers, developing an easy process for locally debugging this integration may be somewhat difficult.
Attributions:
query!
macro.