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
Currently, if you parse a statement (create) on the client side using our parser and/or the WASM wrapper, you'll get back a normalized string that is intended to be consumed by the SQLite backend. It is not spec compliant, in that in may contain AUTOINCREMENT, STRICT, and other non-compliant SQL elements. These are implementations details. Ideally, we'd have a "spec safe" string method on the AST that would produce a parsed output that could be parsed again safely by the parser. This would make using the parser on the client side much easier, useful, and safe.
brunocalza
changed the title
We need some stringification methods that produce spec-compliant SQL strings from a parsed statement/AST
[GSP-5] We need some stringification methods that produce spec-compliant SQL strings from a parsed statement/AST
Mar 23, 2023
Currently, if you parse a statement (create) on the client side using our parser and/or the WASM wrapper, you'll get back a normalized string that is intended to be consumed by the SQLite backend. It is not spec compliant, in that in may contain AUTOINCREMENT, STRICT, and other non-compliant SQL elements. These are implementations details. Ideally, we'd have a "spec safe" string method on the AST that would produce a parsed output that could be parsed again safely by the parser. This would make using the parser on the client side much easier, useful, and safe.
GSP-5
The text was updated successfully, but these errors were encountered: