db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2319) JDBC url attribute territory accepted and ignored after database create time. Instead, it should throw an error.
Date Tue, 13 Feb 2007 05:59:06 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472540
] 

Mamta A. Satoor commented on DERBY-2319:
----------------------------------------

Seems like this is a generic Derby behavior for attributes (and not specific to territory
attribute) ie attributes that make sense at create database time are ignored if specified
on an existing database. I noticed that behavior with attribute logDevice.

Following ij session creates the database in c:/dellater but it's log in c:/dellater1
$ java -Dij.exceptionTrace=true org.apache.derby.tools.ij
ij version 10.3
ij> connect 'jdbc:derby:c:/dellater/db1;create=true;logDevice=c:/dellater1';
ij> exit;

Now, if I try to specify a new location for log on the existing database, it simply gets ignored.
Log continues to stay in c:/dellater1 even after following ij session and no error is generated
for specifying logDevice attribute for the existing database.
$ java -Dij.exceptionTrace=true org.apache.derby.tools.ij
ij version 10.3
ij> connect 'jdbc:derby:c:/dellater/db1;logDevice=c:/dellater';
ij> exit;

> JDBC url attribute territory accepted and ignored after database create time. Instead,
it should throw an error.
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2319
>                 URL: https://issues.apache.org/jira/browse/DERBY-2319
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.3.0.0
>            Reporter: Mamta A. Satoor
>            Priority: Minor
>
> As per Reference Manual, territory attribute can be specified only at database creation
time/upgrade time. 
> I created a database with territory=fr. Later, I connected back to the existing database
with a new value for territory=it. There was no error thrown for the territory attribute.
The services.properties file continued to have the territory specified at the database create
time, ie derby.serviceLocale=fr but I had expected to see an error when a user attempts to
change the territory attribute later on,
> eg
> $ java -Dij.exceptionTrace=true org.apache.derby.tools.ij
> ij version 10.3
> ij> connect 'jdbc:derby:c:/dellater/db1;create=true;territory=fr';
> ij> exit;
> Try to give territory attribute again
> $ java -Dij.exceptionTrace=true org.apache.derby.tools.ij
> ij version 10.3
> ij> connect 'jdbc:derby:c:/dellater/db1;territory=it';
> ij> exit;

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message