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
I know this library is primarily for MySQL dialects, but this is the only PHP SQL parser I could find...
This can't parse the 'custom' Postgres dump, but I found it can sort of parser the plain text format with varying results.
The parser seems to stop after the first timestamp column (it parsed created_at) so I have a bunch of table create statements with only two columns:
CREATETABLEpublic.urls (
id integerNOT NULL,
created_at timestamp(0) without time zone,
updated_at timestamp(0) without time zone,
long_url textNOT NULL
);
Any ideas why?
Thanks!
The text was updated successfully, but these errors were encountered:
@williamdes, thanks for the response. I ended up implementing a solution that didn't involve parsing Postgres dumps.
I understand if this is out-of-scope and you'd like to close the issue, just figured I raise it in case others experienced the same thing. I dug around a bit but unfortunately this is a little over my head
I understand if this is out-of-scope and you'd like to close the issue, just figured I raise it in case others experienced the same thing. I dug around a bit but unfortunately this is a little over my head
williamdes
changed the title
Parser fails on Postgres dumps with timezone columns
Support for special syntaxes for example in SQL_MODE='ORACLE'
Mar 9, 2023
Hello!
I know this library is primarily for MySQL dialects, but this is the only PHP SQL parser I could find...
This can't parse the 'custom' Postgres dump, but I found it can sort of parser the plain text format with varying results.
The parser seems to stop after the first timestamp column (it parsed
created_at
) so I have a bunch of table create statements with only two columns:Any ideas why?
Thanks!
The text was updated successfully, but these errors were encountered: