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
But it provides not only the result but also some addons — at least the first line contains + database schema db-name text. So the resulting file can't be used for import without additional (trivial) editing.
That is very inconvenient for the automation of these tasks with export (backup).
Current Workaround
Export the file.
Delete the first line.
Import the file.
Proposed Solution
Make it possible to export the file ready to be imported. With the same or different (e.g. "export") single command.
Problem to Solve
We have an export feature that includes
database schema {db-name}
command.But the output of the command is straight to the console.
While for export we would like to have a file output. Especially if we have a long schema that can't fit the console.
We can go with the following:
But it provides not only the result but also some addons — at least the first line contains
+ database schema db-name
text. So the resulting file can't be used for import without additional (trivial) editing.That is very inconvenient for the automation of these tasks with export (backup).
Current Workaround
Proposed Solution
Make it possible to export the file ready to be imported. With the same or different (e.g. "export") single command.
Additional Information
schema_cti.tql.zip
The text was updated successfully, but these errors were encountered: