You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
LibSQL would like to remain compatible as long as possible with sqlite. However, PRs such as #87 tend to break compatibility. The feature it offers is great though. This is why i suggest having an "extra" branch where releases containing incompatible changes are merged so that people get to enjoy a power version of sqlite.
The text was updated successfully, but these errors were encountered:
I think that it's fine to diverge in a way that #87 does it -- sqlite_module has a version number, so the existing code remains compatible, and only upgrades when the authors want it. A second branch would be a good idea, but it also doubles the maintainership burden, so for now I'd rather stick to a single main branch, and keep it as compatible as possible, but not at all costs (e.g. #87 is definitely good enough to just go in).
88: improve syntax error message r=penberg a=MarinPostma
improve the error message when a syntax error is encountered.
The parser is a bit sloppy when it comes to reporting the error locations, sometimes pointing farther than he should. I'll see if this is fixable later, or if this is a feature of the lemon parser 😄
the error message looks like:
```
>> echo '{"statements": ["selecct count(*) from test where x = 12"]}' | http post "127.0.0.1:8080"
{"error":"syntax error around L1:8: `selecct`"}
```
Co-authored-by: ad hoc <postma.marin@protonmail.com>
LibSQL would like to remain compatible as long as possible with sqlite. However, PRs such as #87 tend to break compatibility. The feature it offers is great though. This is why i suggest having an "extra" branch where releases containing incompatible changes are merged so that people get to enjoy a power version of sqlite.
The text was updated successfully, but these errors were encountered: