Skip to content

[GSP-5] We need some stringification methods that produce spec-compliant SQL strings from a parsed statement/AST #41

Open

Description

@carsonfarmer

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

Activity

  1. 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[/+] on Mar 23, 2023
  2. sanderpick commented on Apr 7, 2023

    @sanderpick
    Contributor

    @carson is this issue still a thing? (i'm trying to clean up triage issues)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingenhancementNew feature or requestlinearSync issue with linear

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions