Hi Jean,
I wonder if there is a universal way of specifying "\r" in Java like there
is for file separator. File.separator is portable on different platforms.
Mamta
On 3/10/07, Jean T. Anderson <[EMAIL PROTECTED]> wrote:
Mamta Satoor wrote:
> Jean, what you are experiencing is the expected be
I agree with Bernt that the optimizer override syntax will be more intuitive
with /*..*/ form of comments. With the current -- syntax, you can be taken
by surprise if one forgets that everything after -- is considered comment
and hence the actual sql should not be included there.
Mamta
On 3/10/
I think this discussion is another arument for
https://issues.apache.org/jira/browse/DERBY-1749
Then an example could be
ResultSet rs = s.executeQuery(
"SELECT num, addr FROM derbyDB /*derby-properties index=IDX1*/ order by
num");
while
"SELECT num, addr FROM derbyDB /*derby-properties
Bryan Pendleton wrote:
>> In my post I should have said "I also showed two queries that are
>> expected to get syntax errors." --I'm not sure that sample invalid
>> syntax needs to be put into the docs.
>>
>> Is there any feedback on using the "\r" ? In the back of my mind I'm
>> thinking that won'
In my post I should have said "I also showed two queries that are
expected to get syntax errors." --I'm not sure that sample invalid
syntax needs to be put into the docs.
Is there any feedback on using the "\r" ? In the back of my mind I'm
thinking that won't be portable between Windows and Unix.
Mamta Satoor wrote:
> Jean, what you are experiencing is the expected behavior.
Hi, Mamta,
Yes -- sorry I should have been more clear in my post. It's clearly
documented that the derby-properties clause must come in the right place
(ie. after the table name to specify the index) and that it must
