Title: [GSP-5] We need some stringification methods that produce spec-compliant SQL strings from a parsed statement/AST · Issue #41 · tablelandnetwork/go-sqlparser · GitHub
Open Graph Title: [GSP-5] We need some stringification methods that produce spec-compliant SQL strings from a parsed statement/AST · Issue #41 · tablelandnetwork/go-sqlparser
X Title: [GSP-5] We need some stringification methods that produce spec-compliant SQL strings from a parsed statement/AST · Issue #41 · tablelandnetwork/go-sqlparser
Description: 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...
Open Graph Description: 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. ...
X Description: 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 backe...
Opengraph URL: https://github.com/tablelandnetwork/go-sqlparser/issues/41
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[GSP-5] We need some stringification methods that produce spec-compliant SQL strings from a parsed statement/AST","articleBody":"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.\n\n\u003csub\u003e[GSP-5](https://linear.app/tableland/issue/GSP-5/we-need-some-stringification-methods-that-produce-spec-compliant-sql)\u003c/sub\u003e","author":{"url":"https://github.com/carsonfarmer","@type":"Person","name":"carsonfarmer"},"datePublished":"2022-12-13T18:49:11.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/41/go-sqlparser/issues/41"}| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:1898db73-399b-a710-8e11-c51dfc2f84c2 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | B14A:778F9:29FA66F:3651CC5:6992A654 |
| html-safe-nonce | 002b0e3207eb79b2a8866fcb2f67aa065d6367d50c1aa51fc9dfb282511a5fe4 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJCMTRBOjc3OEY5OjI5RkE2NkY6MzY1MUNDNTo2OTkyQTY1NCIsInZpc2l0b3JfaWQiOiI3NzcwMDkzNzQ3MjAzOTA5MjA0IiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | 734bfe6dd8b3c5125d4282486897277472a7293bfd1cc015121371e9f02536c7 |
| hovercard-subject-tag | issue:1494955011 |
| github-keyboard-shortcuts | repository,issues,network-graph,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/tablelandnetwork/go-sqlparser/41/issue_layout |
| twitter:image | https://opengraph.githubassets.com/b5f2aff1762cc5ef75d9b593f9904108c2d668c6e65eee3e1adf0e48d56532e4/tablelandnetwork/go-sqlparser/issues/41 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/b5f2aff1762cc5ef75d9b593f9904108c2d668c6e65eee3e1adf0e48d56532e4/tablelandnetwork/go-sqlparser/issues/41 |
| og:image:alt | 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. ... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | carsonfarmer |
| hostname | github.com |
| expected-hostname | github.com |
| None | 42c603b9d642c4a9065a51770f75e5e27132fef0e858607f5c9cb7e422831a7b |
| turbo-cache-control | no-preview |
| go-import | github.com/tablelandnetwork/go-sqlparser git https://github.com/tablelandnetwork/go-sqlparser.git |
| octolytics-dimension-user_id | 99691591 |
| octolytics-dimension-user_login | tablelandnetwork |
| octolytics-dimension-repository_id | 501423846 |
| octolytics-dimension-repository_nwo | tablelandnetwork/go-sqlparser |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 501423846 |
| octolytics-dimension-repository_network_root_nwo | tablelandnetwork/go-sqlparser |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 848bc6032dcc93a9a7301dcc3f379a72ba13b96e |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width