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 the lib support different databases (postgresql-sql, mysql , etc .. ) dialect only in the tokenizer.
My question is - if there was any discussions/plans about supporting per-db dialects also in the parser (or do you you think it's god idea to start such discussions )?
Where most of the DB's support ANSI sql , when it's come to more advance features like json-parsing - There is great variability between the different databases
The text was updated successfully, but these errors were encountered:
Hi ,
Currently the lib support different databases (postgresql-sql, mysql , etc .. ) dialect only in the tokenizer.
My question is - if there was any discussions/plans about supporting per-db dialects also in the parser (or do you you think it's god idea to start such discussions )?
Where most of the DB's support ANSI sql , when it's come to more advance features like json-parsing - There is great variability between the different databases
The text was updated successfully, but these errors were encountered: