It because the spec is crud.

if using dialect 1 then any case is converted to uppercase and therefore
accepted.

if using dialect 3 then the case must match exactly and identifiers must
have quotes.

However, if the identifier is all uppercase then it cant have quote.... note
CANT.

To top it all, every component writer makes different assumptions about it
converting case and adding/removing quotes in a non-structured fashion.

----- Original Message -----
From: "Nando Dessena" <nandod@...>
To: <ib-support@yahoogroups.com>
Sent: Wednesday, 11 April 2001 21:12
Subject: Re: [ib-support] uppercase and double quotes


> Jordi,
>
> > CREATE TABLE "empleado" (
> > "dni" INTEGER NOT NULL,
> > "nombre" VARCHAR(50));
>
> > select * from EMPLEADO => ERROR!
> > select * from empleado => ERROR!
> > select * from "EMPLEADo" => ERROR!
> > select * from "EMPLEADO" => ERROR!
> > select * from "empleado" => WORKS!
> >
> > But if database objects are declared without double quotes:
> >
> > CREATE TABLE empleado (
> > dni INTEGER NOT NULL,
> > nombre VARCHAR(50));
>
> > select * from EMPLEADO => WORKS!
> > select * from empleado => WORKS!
> > select * from "EMPLEADo" => ERROR!
> > select * from "EMPLEADO" => WORKS!
> > select * from "empleado" => ERROR!
> >
> > What happens? is it an Interbase bug or the problem is in IBExpert or
maybe
> > the Gemini ODBC?
>
> to me, it is exactly as designed/implemented/advertised.
> What is it exactly that you find wrong in the results?
> --
> ____
> _/\/ando
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>