Subject | Re: [IBO] TableNames doublequoted??, why??? |
---|---|
Author | Helen Borrie |
Post date | 2005-05-31T23:45:40Z |
At 05:40 PM 31/05/2005 +0000, you wrote:
versions. Double-quoted identifiers are optional (except when "illegal"
characters are used in the identifier) but some database tools enforce
double quotes by default. When DQ identifiers are used, all references to
them in SQL must include the DQ's.
Since DQ identifiers are also case-sensitive, the two versions of the
database are not equivalent.
For example,
create table "aTable" ("id" integer, "data" varchar(20))
is different from
create table aTable(id integer, data varchar(20))
Helen
>Hi there...It will be the result of using different tools to create the two database
>
>i've found some databases where in the sentences i must double quote
>the table and field names like this:
>
>INSERT INTO "VENTAS" ("ARTICULO","CANTIDAD","ETC") VALUES
>('XYZ',789','ETC')
>
>but in another version of this database the sentences are acepted
>without the double quoted... like this:
>
>INSERT INTO PROPIEDADES (TIPO,PISOS,APTOS,ASCEN) VALUES ('E',10,32,3)
>
>why happen this???... both databases uses the Dialect 3, and same page
>size... wich is the factor that makes this behaviour??
versions. Double-quoted identifiers are optional (except when "illegal"
characters are used in the identifier) but some database tools enforce
double quotes by default. When DQ identifiers are used, all references to
them in SQL must include the DQ's.
Since DQ identifiers are also case-sensitive, the two versions of the
database are not equivalent.
For example,
create table "aTable" ("id" integer, "data" varchar(20))
is different from
create table aTable(id integer, data varchar(20))
Helen