Okay, my assumptions about Oracle were incorrect there. (I shouldn't have
Oracle, since I have very little experience with it.)
However, Sybase ASE seems to be very strict with this. If I use Sybase's
SQL tool to execute a command, where I have a table named "ETSUser":
select * from ETSUser
No problem, I get my result set. However, If I do this:
select * from etsuser
I get an error back from the database. This is the type of thing JAWS is
doing in the 2.4 beta... But only for the custom finder SQL that I have
specified in jaws.xml. (The CMP generated parts are correct.)
Mike
----- Original Message -----
From: "Victor Langelo" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, June 28, 2001 12:31 PM
Subject: Re: [JBoss-user] LOCKING-WAITING after setRollbackOnly()
> Michael Jara wrote:
>
> > Yes, Sybase ASE is case sensitive as to table and column names. (SQL
> > keywords may be any case.) I beleive this is not unique to Sybase, but
is
> > also the case in some other database servers such as Oracle. JAWS in
JBoss
> > 2.2.2 works properly, but Beta 2.4 does not... I get SQL errors, and
the
> > trace shows all of the finder text from my jaws.xml file to be
lower-cased.
> >
>
> In Oracle, object names (table, columns, packages, functions, etc) are
only case
> sensitive if you enclose them in double quotes in your SQL. Otherwise they
are
> converted to upper case.
>
> --Victor
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
