Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
ermodeler - We want this command to provide operations on ermodeler files such as { generateERModelFromDatabase, convertModel, generateSQLScriptFromModel }. This command will allow a user to extract the schema of one database/vendor, transform the schema to a new database/vendor, generate the DDL for the new source and then execute it with the \source command.
As in ADStudio 12 RC 22-8, the in-progress version of the \erm command, in the name section from the man page does not respect the pattern from #6837.
As in ADStudio 12 RC 22-8, the in-progress version of the \erm command, in the name section from the man page does not respect the pattern from #6837.
major work complete. Working on cleaning up exceptions and error handling and removing debugging information.
major work complete. Working on cleaning up exceptions and error handling and removing debugging information.
The QA team can write some unit test scripts like the below
\source convert_file.fluid
--- convert_file.fluid ---
erm -extract -mysqldb -mysqlfile.xed
erm -convert -oracle -oraclefile.xed
erm -generateddl -ddlfile.sql
The QA team can write some unit test scripts like the below
\source convert_file.fluid
--- convert_file.fluid ---
erm -extract -mysqldb -mysqlfile.xed
erm -convert -oracle -oraclefile.xed
erm -generateddl -ddlfile.sql
The implementation of \erm command is done but is disabled, hence, you won't be able to test it at the moment. SVN r30625. Reassign this issue to Niels so that he can enable this feature in the future release.
Known Problems:
(1) Pressing CTRL-C to stop a running \erm command
\erm is built on top of ADS ERM code to leverage the following operations:
(1-a) retrieve database schema objects,
(1-b) read/write XML file
(1-c) generate DDL statements
In the current ADS ERM implementation, only (1-a) supports thread interruption, but not (1-b) and (1-c). Hence, \erm command does not really support CTRL-C.
(2) Difference of XML <Place> elements between .xed files generated by ADS and \erm:
The contents of .xed files generated by ADS and \erm might not be the same when given exactly the same input conditions. If you run 'diff' command on the generated .xed files, you might find the location defined in <Place> elements are not the same; this means when you open the .xed file generated by \erm in ADS, database objects will be displayed at different locations. However, the definition of database objects should always be no difference.
(3) Reading .xed file from standard input
\erm currently can write output to standard output but cannot read input from standard input. This means you cannot run a pipeline like the one shown below:
prompt> \erm --extract | \erm --convert 'MS SQL Server' 2012 | \erm --generate
The implementation of \erm command is done but is disabled, hence, you won't be able to test it at the moment. SVN r30625. Reassign this issue to Niels so that he can enable this feature in the future release.
Known Problems:
(1) Pressing CTRL-C to stop a running \erm command
\erm is built on top of ADS ERM code to leverage the following operations:
(1-a) retrieve database schema objects,
(1-b) read/write XML file
(1-c) generate DDL statements
In the current ADS ERM implementation, only (1-a) supports thread interruption, but not (1-b) and (1-c). Hence, \erm command does not really support CTRL-C.
(2) Difference of XML <Place> elements between .xed files generated by ADS and \erm:
The contents of .xed files generated by ADS and \erm might not be the same when given exactly the same input conditions. If you run 'diff' command on the generated .xed files, you might find the location defined in <Place> elements are not the same; this means when you open the .xed file generated by \erm in ADS, database objects will be displayed at different locations. However, the definition of database objects should always be no difference.
(3) Reading .xed file from standard input
\erm currently can write output to standard output but cannot read input from standard input. This means you cannot run a pipeline like the one shown below:
prompt> \erm --extract | \erm --convert 'MS SQL Server' 2012 | \erm --generate
Issue #7701 |
| In Progress |
Completion |
| No due date |
| Fixed Build trunk/30625 |
| No time estimate |
1 issue link |
relates to #7704
Issue #7704Add FluidShell command sqldump |