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
Hello, many thanks for the awesome DB designer tool.
Is there a way after importing from the SQL statement to work with the project completely with AML?
Current flow
Import existing database structure from SQL
Want to create a feature that requires DB changes
Selecting update your schema suggests creating a new source instead of populating current from SQL
The text was updated successfully, but these errors were encountered:
Thanks for reaching out.
I see what you mean. I had in mind to allow editing SQL for some time but as it could be quite big and long to parse it seems hardly feasible (in fact I even stopped storing it raw to lighten a bit big projects). Also I think it's better to keep imported sources free from modifications so they reflect the real current state (you can re-import them to evolve them).
My thoughts were to allow AML to define but also "modify" the merged schema. That's why update your schema suggest creating an AML source. It works quite well if you need to add tables or columns but for updating or deleting columns it doesn't work.
With the export feature (lightning on the top right > export your schema > all tables > AML) you get something similar. You can create a project with your SQL and export all tables as AML and the create a source or project from this AML.
But clearly it would be nice if the Azimutt CLI could do that. But I would need an SQL parser in JS (now it's only in Elm) and an AML generator in JS (also only in Elm for now) ^^ This will definitely happen but not sure when ^^ At least you have a workaround ;)
Hello, many thanks for the awesome DB designer tool.
Is there a way after importing from the SQL statement to work with the project completely with AML?
Current flow
update your schema
suggests creating a new source instead of populating current from SQLThe text was updated successfully, but these errors were encountered: