I'm fairly sure that the SQL-92 spec calls for case insensitive column names
(but don't quote me on that cause I'm not 100% sure).  Also, since I'm in a
UNIX shop switching to Microsoft is not really an option (even *if* I wanted
to) - but thats not really the point.

More importantly, I'm aware I can change the post-deployment descriptor
created by Orion but thats a major pain-in-da-behind if I'm doing
development and want to redeploy several times.  When I've tried putting an
partial orion-ejb-jar.xml into the package, its never worked right, implying
that I need to copy a previously deployed version to modify - again
extremely cumbersome.

I was hoping that there was some way to do this without slicing up the
post-deployment orion generated files. 

-----Original Message-----
From: Hani Suleiman [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 28, 2001 10:26 AM
To: Orion-Interest <[EMAIL PROTECTED]>; Aaron Tavistock
Subject: Re: [orion-interest]EJB2.0 spec or implementation?


On 28/12/01 12:56 pm, "Aaron Tavistock" <[EMAIL PROTECTED]> wrote:

> So heres the story - database field names are case insensitive, so common
> parlance for representing a space is an underscore (e.g. 'this_field').

Nope. MS SQLServer is not case insensitive. You could always tweak
orion-ejb-jar.xml to map it to whatever column names your heart desires


Reply via email to