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
Describe the bug
Not sure if this is a bug or rather a feature request, but since many datatypes exists that are not directy supported in the importar, it could be useful to import the type as is in the sql file instead of clearing that information.
To Reproduce
Steps to reproduce the behavior:
Import a column in a not supported datatype (es. numrange in PostgreSQL)
See that the datatype is empty in the resulting table
Expected behavior
Keep that type. If the json is edited manually, the datatype can be set and shown in the diagram.
Additional context
Perhaps making the datatype field editable besides having some autocomplete suggestions could avoid the issue.
The text was updated successfully, but these errors were encountered:
Describe the bug
Not sure if this is a bug or rather a feature request, but since many datatypes exists that are not directy supported in the importar, it could be useful to import the type as is in the sql file instead of clearing that information.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Keep that type. If the json is edited manually, the datatype can be set and shown in the diagram.
Additional context
Perhaps making the datatype field editable besides having some autocomplete suggestions could avoid the issue.
The text was updated successfully, but these errors were encountered: