Finding a simple solution was my knee jerk reaction. I'm not anywhere near
a database expert, having spent most of my time in Interbase and Sybase, but
I am a little confused as to why firebird allows case sensitive columns
here. I know sybase isn't going to let you specify one way or the other -
its all case insensitive.

Then again, I guess it doesn't matter. The point is that we have a bunch of
clients out there, and if we change the rules then we'll break code.

I still don't understand the issue completely, however. SQL dialect 1 is
case insensitive and dialect 3 is case sensitive, is that right? Can't we
just detect which dialect we are in (say, when we connect to the database)?
If we're in 3, we look for an exact match and if its in 1 we uppercase the
thing.

Just thoughts from one who don't know :-)

>From: "John Lister" <lister-filter@...>
>Reply-To: Firebird-Java@yahoogroups.com
>To: Firebird-Java@yahoogroups.com
>Subject: [Firebird-Java] Re: decision help needed
>Date: Thu, 17 Oct 2002 00:38:49 -0000
>
>What do the other firebird tools do when field names are quoted? If
>it is possible to determine if a field is quoted or not then we
>should either perform a fixed conversion (eg to uppercase) or pass
>the value directly. I would be concerned that if i enter names in
>isql for example that i have to remember to quote them (or not) in my
>java code. I think we need to find a simple solution, otherwise we
>will be implementing numerous checks and conversions that have been
>used in the past... Although i do like compatibility between
>interclient and jaybird for example, this is probably a point where
>we can place a marker in the ground and not cross it?
>
>JOHN
>
>
>

_________________________________________________________________
Surf the Web without missing calls! Get MSN Broadband.
http://resourcecenter.msn.com/access/plans/freeactivation.asp