Subject | Re: [IBO] Re: TIB_Query Programatically Defined SQL with Strings |
---|---|
Author | Helen Borrie |
Post date | 2003-12-08T22:43Z |
At 10:20 PM 8/12/2003 +0000, Marco Menardi wrote:
If I run a DSQL or a script like
create table ATable (
id integer,
data varchar(40));
Then the table will be stored as ATABLE and the columns will be ID and DATA
and Fb/IB doesn't care about case. In any query I can do
insert into ATable (id, data)
values (99, 'This is some data');
The only time case sensitivity matters is when you actually **define** the
objects with quoted identifiers. This would have made my identifiers
case-sensitive:
create table "ATable" (
"id" integer,
"data" varchar(40));
There seems to be a lot of confusion around this, partly caused by some
third-party tools that force you to use double-quotes for everything. You
don't have this problem with IB_SQL.
Helen
>Use UPPER CASE for your table and field name, in your databaseMarco, this is not true.
>definition, otherwise you have to enclose into double quotes at the
>client side (i.e. update "MyTable" set "MyField" = 'ABC company')
If I run a DSQL or a script like
create table ATable (
id integer,
data varchar(40));
Then the table will be stored as ATABLE and the columns will be ID and DATA
and Fb/IB doesn't care about case. In any query I can do
insert into ATable (id, data)
values (99, 'This is some data');
The only time case sensitivity matters is when you actually **define** the
objects with quoted identifiers. This would have made my identifiers
case-sensitive:
create table "ATable" (
"id" integer,
"data" varchar(40));
There seems to be a lot of confusion around this, partly caused by some
third-party tools that force you to use double-quotes for everything. You
don't have this problem with IB_SQL.
Helen