-
Notifications
You must be signed in to change notification settings - Fork 271
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
sync cr-sqlite to ext/crr #151
Conversation
thanks @tantaman! How can I verify that everything works, manually? I tried going to |
hmm. Let me double check that I got everything. |
(btw -- you need to be on the Rust nightly toolchain. Let me add an item to add +nightly to the makefile so you don't need to change your default toolchain)
Rust tests are in
|
@tantaman maybe you have |
@psarna - Hah, yeah. The .gitignore file in the libsql root excludes https://github.com/libsql/libsql/blob/7ecf22a1a61e13655427b576c3a2a7c9f1ef485b/.gitignore#L3-L5
|
this import of cr-sql also depends on a bundled sqlite3.c amalgamation which is rightfully ignored by libsql. I'll need to update my make target to depend on Will let you know when to check back. |
Ah, right. Feel free to also amend the .gitignore file so it explicitly ignores all the Makefiles that make sense, while preserving e.g. ones from ext/ |
I ran `./configure` and the only generated Makefile was in the root of the project. afaik this is the only generate makefile that needs ignoring.
@psarna - Looks good now with the exception that See linked terminal output in the build & test repro (from a fresh clone this time) below.
[1] https://app.warp.dev/block/kv1cWBgm8AkKrtbXvhaa0c |
thanks, I'll go over the warnings and fix, and meanwhile let's just wait for CI to finish and we can merge the initial PR! |
@tantaman which flags did you use to ./configure libsql before running |
149: http params: support bool r=MarinPostma a=MarinPostma Support for bools in http params close #146 151: Include content-type header for query response. r=MarinPostma a=BearLemma One thing I'm not sure about is whether it's necessary to include the encoding in the header as well 🤔 Co-authored-by: ad hoc <postma.marin@protonmail.com> Co-authored-by: Jan Plhak <jp@chiselstrike.com>
#147
copy
cr-sqlite
extension code as-is toext/crr
build & test
https://app.warp.dev/block/FWDFdN9HSg4jaHayk3EwBo
https://app.warp.dev/block/lseqHcw4cpmyqWMBsyexs5
Next steps:
src/sqlite/shell.c,sqlite3.c,sqlite3.h,sqlite3ext.h
and use the files present inlibsql
commit_hook
create crr
syntaxNote: the
package.json
and otherjs
files are for distribution of this extension on npm.There are also a number of integration tests in Python and TypeScript (using https://github.com/dubzzz/fast-check) not included here. I'm thinking of the best way to include those.