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
This is a big help. It parses without throwing an exception now! I think there's still room for improvement in understanding the meaning of the Postgres schema. For example, the DDL contains
ALTER TABLE ONLY public.accounts ADD CONSTRAINT accounts_username_key UNIQUE (username);
But in the parsed output, we see:
{'name': 'username',
'type': 'character varying',
'size': 50,
'references': None,
'unique': False, <======= should be True?
'nullable': False,
'default': None,
'check': None},
But the bug I reported is fixed, so closing this issue.
The text was updated successfully, but these errors were encountered:
Issue was reported here: #99
This is a big help. It parses without throwing an exception now! I think there's still room for improvement in understanding the meaning of the Postgres schema. For example, the DDL contains
ALTER TABLE ONLY public.accounts ADD CONSTRAINT accounts_username_key UNIQUE (username);
But in the parsed output, we see:
{'name': 'username',
'type': 'character varying',
'size': 50,
'references': None,
'unique': False, <======= should be True?
'nullable': False,
'default': None,
'check': None},
But the bug I reported is fixed, so closing this issue.
The text was updated successfully, but these errors were encountered: