Re: Case Sensitivity

2010-03-24 Thread Peter Ondruška
select
Id as id,
Code as code,
TypeStr as typeStr
  from MyTable

On Wed, Mar 24, 2010 at 10:30 PM, Pavel Bortnovskiy
pbortnovs...@jefferies.com wrote:

 Hello, all:

 when executing a statement, such as:

                         select
                     Id as id,
                     Code as code,
                     TypeStr as typeStr
                   from MyTable

 against a Derby in-memory table, the ResultSetMetaData present column names
 all in upper case and the original case is not preserved.

 Is there a setting which would allow to preserve the case specified in the
 SQL statement, i.e. with the statement above, the first column would be
 id, second - code, third - typeStr, etc...

 Thank you,

 Pavel.



 Jefferies archives and monitors outgoing and incoming e-mail. The contents
 of this email, including any attachments, are confidential to the ordinary
 user of the email address to which it was addressed. If you are not the
 addressee of this email you may not copy, forward, disclose or otherwise use
 it or any part of it in any form whatsoever. This email may be produced at
 the request of regulators or in connection with civil litigation. Jefferies
 accepts no liability for any errors or omissions arising as a result of
 transmission. Use by other than intended recipients is prohibited.  In the
 United Kingdom, Jefferies operates as Jefferies International Limited;
 registered in England: no. 1978621; registered office: Vintners Place, 68
 Upper Thames Street, London EC4V 3BJ.  Jefferies International Limited is
 authorised and regulated by the Financial Services Authority.


Re: Case Sensitivity

2010-03-24 Thread Pavel Bortnovskiy
Thank you, Peter, for your prompt response. Is enclosing them in quotes 
the only way to do so? Is there any setting which can be applied to Derby 
(or a -Define), so that the quotes could be omitted?






Peter Ondru?ka peter.ondru...@gmail.com 
03/24/2010 05:33 PM
Please respond to
Derby Discussion derby-user@db.apache.org


To
Derby Discussion derby-user@db.apache.org
cc

Subject
Re: Case Sensitivity






select
Id as id,
Code as code,
TypeStr as typeStr
  from MyTable

On Wed, Mar 24, 2010 at 10:30 PM, Pavel Bortnovskiy
pbortnovs...@jefferies.com wrote:

 Hello, all:

 when executing a statement, such as:

 select
 Id as id,
 Code as code,
 TypeStr as typeStr
   from MyTable

 against a Derby in-memory table, the ResultSetMetaData present column 
names
 all in upper case and the original case is not preserved.

 Is there a setting which would allow to preserve the case specified in 
the
 SQL statement, i.e. with the statement above, the first column would be
 id, second - code, third - typeStr, etc...

 Thank you,

 Pavel.



 Jefferies archives and monitors outgoing and incoming e-mail. The 
contents
 of this email, including any attachments, are confidential to the 
ordinary
 user of the email address to which it was addressed. If you are not the
 addressee of this email you may not copy, forward, disclose or otherwise 
use
 it or any part of it in any form whatsoever. This email may be produced 
at
 the request of regulators or in connection with civil litigation. 
Jefferies
 accepts no liability for any errors or omissions arising as a result of
 transmission. Use by other than intended recipients is prohibited.  In 
the
 United Kingdom, Jefferies operates as Jefferies International Limited;
 registered in England: no. 1978621; registered office: Vintners Place, 
68
 Upper Thames Street, London EC4V 3BJ.  Jefferies International Limited 
is
 authorised and regulated by the Financial Services Authority.






Jefferies archives and monitors outgoing and incoming e-mail. The contents of 
this email, including any attachments, are confidential to the ordinary user of 
the email address to which it was addressed. If you are not the addressee of 
this email you may not copy, forward, disclose or otherwise use it or any part 
of it in any form whatsoever. This email may be produced at the request of 
regulators or in connection with civil litigation. Jefferies accepts no 
liability for any errors or omissions arising as a result of transmission. Use 
by other than intended recipients is prohibited.  In the United Kingdom, 
Jefferies operates as Jefferies International Limited; registered in England: 
no. 1978621; registered office: Vintners Place, 68 Upper Thames Street, London 
EC4V 3BJ.  Jefferies International Limited is authorised and regulated by the 
Financial Services Authority.

Re: Case Sensitivity

2010-03-24 Thread Peter Ondruška
Not that I know, this is by SQL standard.

On Wed, Mar 24, 2010 at 10:43 PM, Pavel Bortnovskiy 
pbortnovs...@jefferies.com wrote:


 Thank you, Peter, for your prompt response. Is enclosing them in quotes the
 only way to do so? Is there any setting which can be applied to Derby (or a
 -Define), so that the quotes could be omitted?





 *Peter Ondruška peter.ondru...@gmail.com*

 03/24/2010 05:33 PM
 Please respond to
 Derby Discussion derby-user@db.apache.org

   To
 Derby Discussion derby-user@db.apache.org
 cc
   Subject
 Re: Case Sensitivity




 select
Id as id,
Code as code,
TypeStr as typeStr
  from MyTable

 On Wed, Mar 24, 2010 at 10:30 PM, Pavel Bortnovskiy
 pbortnovs...@jefferies.com wrote:
 
  Hello, all:
 
  when executing a statement, such as:
 
  select
  Id as id,
  Code as code,
  TypeStr as typeStr
from MyTable
 
  against a Derby in-memory table, the ResultSetMetaData present column
 names
  all in upper case and the original case is not preserved.
 
  Is there a setting which would allow to preserve the case specified in
 the
  SQL statement, i.e. with the statement above, the first column would be
  id, second - code, third - typeStr, etc...
 
  Thank you,
 
  Pavel.
 
 
 
  Jefferies archives and monitors outgoing and incoming e-mail. The
 contents
  of this email, including any attachments, are confidential to the
 ordinary
  user of the email address to which it was addressed. If you are not the
  addressee of this email you may not copy, forward, disclose or otherwise
 use
  it or any part of it in any form whatsoever. This email may be produced
 at
  the request of regulators or in connection with civil litigation.
 Jefferies
  accepts no liability for any errors or omissions arising as a result of
  transmission. Use by other than intended recipients is prohibited.  In
 the
  United Kingdom, Jefferies operates as Jefferies International Limited;
  registered in England: no. 1978621; registered office: Vintners Place, 68
  Upper Thames Street, London EC4V 3BJ.  Jefferies International Limited is
  authorised and regulated by the Financial Services Authority.





 Jefferies archives and monitors outgoing and incoming e-mail. The contents
 of this email, including any attachments, are confidential to the ordinary
 user of the email address to which it was addressed. If you are not the
 addressee of this email you may not copy, forward, disclose or otherwise use
 it or any part of it in any form whatsoever. This email may be produced at
 the request of regulators or in connection with civil litigation. Jefferies
 accepts no liability for any errors or omissions arising as a result of
 transmission. Use by other than intended recipients is prohibited.  In the
 United Kingdom, Jefferies operates as Jefferies International Limited;
 registered in England: no. 1978621; registered office: Vintners Place, 68
 Upper Thames Street, London EC4V 3BJ.  Jefferies International Limited is
 authorised and regulated by the Financial Services Authority.



Re: Case Sensitivity

2010-03-24 Thread Mark Thornton

Peter Ondruška wrote:

Not that I know, this is by SQL standard.

On Wed, Mar 24, 2010 at 10:43 PM, Pavel Bortnovskiy 
pbortnovs...@jefferies.com mailto:pbortnovs...@jefferies.com wrote:



Thank you, Peter, for your prompt response. Is enclosing them in
quotes the only way to do so? Is there any setting which can be
applied to Derby (or a -Define), so that the quotes could be omitted?

Databases like SQLServer that do preserve the case violate the standard 
by ignoring the case of quoted identifiers. On a standard conforming 
database, converting unquoted identifiers to upper case is unavoidable.


Mark Thornton