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
| Dev |
|
| QA |
|
| Priority | Major |
| Complexity | Unknown |
| Component | App - FluidShell - Command |
| Version | 12.0 |
s:/home/s/Documents/mysql$ session
ID User Database Server
--------- ---- ---------------- ----------------------------------------------------------------
mysql* root performance_test /home/s/.datastudio/connections/NexGen Servers/MySQL/MySQL 5.5
ora12 sys ORCLB /home/s/.datastudio/connections/NexGen Servers/Oracle/Oracle 11g
ora12ivan IVAN ORCLB /home/s/.datastudio/connections/NexGen Servers/Oracle/Oracle 11g
s:/home/s/Documents/mysql$ select * from iptest limit 25
s:/home/s/Documents/mysql$ sqlexport | sqlimport -k ora12 IVAN.IPTEST
sqlimport: import failed: Table 'IPTEST' is not defined in database 'ORCLB'.
It would be good to add support for fully qualified names. We can use our current code which looks like this :
// Parse the fully qualified table name into database, schema and table
StringBuilder qualifiedTableName = new StringBuilder();
StringBuilder qualifiedSchemaName = new StringBuilder();
StringBuilder qualifiedDatabaseName = new StringBuilder();
StatementParser.fullTableSchemaDatabasePath(...);
Made change on \sqlimport to support fully qualified table name. See Notes session, \sqlimport manual page for more info.
I did not modify \sqlexport to support fully qualified table name(s), \sqlexport can accept 2 more more tables on command line, if \sqlexport also need to support qualified table name(s), please log a separate issue.
Made change on \sqlimport to support fully qualified table name. See Notes session, \sqlimport manual page for more info.
I did not modify \sqlexport to support fully qualified table name(s), \sqlexport can accept 2 more more tables on command line, if \sqlexport also need to support qualified table name(s), please log a separate issue.
We won't support schema names when doing a sqlexport. Users can use "sqlexport -s" to specify schema name
We won't support schema names when doing a sqlexport. Users can use "sqlexport -s" to specify schema name
Issue #7530 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build trunk/29131 |
| No time estimate |
It would be good to add support for fully qualified names. We can use our current code which looks like this :
// Parse the fully qualified table name into database, schema and table
StringBuilder qualifiedTableName = new StringBuilder();
StringBuilder qualifiedSchemaName = new StringBuilder();
StringBuilder qualifiedDatabaseName = new StringBuilder();
StatementParser.fullTableSchemaDatabasePath(...);