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 | 13.0 |
change schema RTELIB
list tables
-> No tables found
DB2 iSeries has a mechanism to change the current schema, but we are not aware of a way to get the current schema. You can see this in ConnectionProperties.getCurrentSchema() & getContextSchema(). We used to not know how to get the current schema for DB2 LUW and zOS, but then found that you could with :
select current schema from sysibm.sysdummy1
This query might work for DB2 iSeries.
EXEC SQL VALUES(CURRENT SCHEMA) INTO :CURSCHEMA
EXEC SQL VALUES(CURRENT SCHEMA) INTO :CURSCHEMA
Current Schema is now extracted from the database and used instead of the currently logged in user name. Fixes the issue
Current Schema is now extracted from the database and used instead of the currently logged in user name. Fixes the issue
Issue #8978 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build 13.0.1.11 |
| No time estimate |
DB2 iSeries has a mechanism to change the current schema, but we are not aware of a way to get the current schema. You can see this in ConnectionProperties.getCurrentSchema() & getContextSchema(). We used to not know how to get the current schema for DB2 LUW and zOS, but then found that you could with :
select current schema from sysibm.sysdummy1
This query might work for DB2 iSeries.