[
https://issues.apache.org/jira/browse/DERBY-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase closed DERBY-2169.
----------------------------
Resolution: Won't Fix
This doesn't seem to be a commonly reported problem. The SQLIdentifier topic in
the Reference Manual says, "identifiers for dictionary objects are limited to
128 characters and are case-insensitive (unless delimited by double quotes),
because they are automatically translated into uppercase by the system." And
the examples for system procedures show the arguments in uppercase.
> Documentation for SYSCS_UTIL procedures should clearly state how to specify
> schema name and table name correctly
> ----------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2169
> URL: https://issues.apache.org/jira/browse/DERBY-2169
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.2.1.6
> Environment: OS X, java version "1.5.0_06"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-112)
> Java HotSpot(TM) Client VM (build 1.5.0_06-64, mixed mode, sharing)
> Reporter: Dieter Wimberger
> Labels: derby_triage10_11
>
> syscs_util.syscs_compress_table throws a "schema does not exist" exception
> for an existing schema.
> Call is made according to the documentation in the reference manual:
> SYSCS_UTIL.SYSCS_COMPRESS_TABLE (IN SCHEMANAME VARCHAR(128),
> IN TABLENAME VARCHAR(128), IN SEQUENTIAL SMALLINT)
> Testcase using ij:
> connect 'jdbc:derby:test;create=true';
> create schema test;
> create table test.test(id varchar(255));
> insert into test.test values('test1');
> insert into test.test values('test2');
> call syscs_util.syscs_compress_table('test','test',0);
> ERROR 38000: The exception 'java.sql.SQLException: Schema 'test' does not
> exist' was thrown while evaluating an expression.
> ERROR 42Y07: Schema 'test' does not exist
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)