Details
-
Bug
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
10.0.2.1, 10.2.1.6
-
None
-
Low
Description
The documentation http://db.apache.org/derby/docs/10.1/tools/ttoolsij30600.html indicates one can set ij properties like ij.maximumDisplayWidth or ij.database in either a properties file indicated with java org.apache.derby.tools.ij -p <filename>, or by using the -Dij.<propertyname>.
However, it appears that instead, the ij.properties in the file are equivalent to properties of the same name in a file or on the commandline, but using -Dij.<propertyname> has no effect.
So, this works:
> java org.apache.derby.tools.ij -p myij.properties
where myij.properties contained the string: maximumDisplayWidth=15
> java org.apache.derby.tools.ij -p myij.properties
where myij.properties contained the string: ij.maximumDisplayWidth=15
> java -DmaximumDisplayWidth=5 org.apache.derby.tools.ij
(and if the setting is like so:
> java -DmaximumDisplayWidth=5 org.apache.derby.tools.ij -p myij.properties
where myij.properties contained the string: ij.maximumDisplayWidth=15 the display width is actually 5)
But this does not work:
> java -Dij.maximumDisplayWidth=5 org.apache.derby.tools.ij
That is, the display width for an ij select remains the default.
I thought this might be a doc bug, but response from the list indicates it is illogical to have a property in a file (eg. ij.maximumDisplayWidth) be superceded by a different property on the command line (eg. -DmaximumDisplayWidth)
I verified that the behavior has been like this since the contribution of derby to apache (10.0)