[DERBY-2319] JDBC url attribute territory accepted and ignored after database create time. Instead, it should throw an error.

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 10.3.1.4
• Component/s: JDBC
• Labels: derby_triage10_5_2
• Urgency: Normal
• Issue & fix info: Repro attached
• Assignee: Unassigned
• Reporter: Mamta A. Satoor
• Created: 10/Feb/07 15:49
• Updated: 15/Feb/11 21:09

Description

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;