tablelandnetwork/go-sqlparser

Issues

• [GSP-9] Feature Request: Geospatial Query Support

  #51 opened a year ago by matthewnanas
  3

• [GSP-4] Generate _per statement_ type diagrams to be used in the spec docs.

  #32 opened 2 years ago by carsonfarmer
  1

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

  #41 opened 2 years ago by carsonfarmer
  1

• [GSP-3] We need to have access to the AST in the wasm parser

  #20 opened 2 years ago by jsign
  4

• [GSP-2] Implement support for prepared statements

  #19 opened 2 years ago by jsign
  1

• [GSP-7] Walk method panics for UPSERT statement

  #50 opened a year ago by brunocalza
  0

• [GSP-8] [GSP-7] Walk method panics for UPSERT statement

  #48 opened a year ago by brunocalza
  0

• [GSP-1] Feature: Add support for extracting the full AST via means _other than_ encoding/json

  #13 opened 2 years ago by carsonfarmer
  0

• Avoid adding extra spaces in encoded string outputs when possible

  #44 opened 2 years ago by carsonfarmer
  0

• Supports parsing custom Tableland functions

  #14 opened 2 years ago by sanderpick
  4

• Drop support for ANY type

  #39 opened 2 years ago by brunocalza
  0

• Allows ENS-like names as identifiers in our SQL parser

  #37 opened 2 years ago by brunocalza
  0

• Support INSERT and UPDATE with SELECT

  #17 opened 2 years ago by jsign
  7

• Allow LEFT/RIGHT JOIN and UNION

  #28 opened 2 years ago by sanderpick
  10

• We need to reconsider supporting FLOAT types in our SQL spec

  #31 opened 2 years ago by jsign
  1

• Implement spec changes that resolve rowid non-determinism

  #27 opened 2 years ago by jsign
  0

• COUNT only works when it is in lowercase

  #24 opened 2 years ago by tansanDOTeth
  1

• Upserts are powerful, but our parser doesn't support UPSERT semantics

  #15 opened 2 years ago by sanderpick
  2

• Double check if we support CASE statements for INSERT/UPDATEs

  #18 opened 2 years ago by jsign
  6