Subject | Re: [ib-support] Why the table name & column name must with double quote? |
---|---|
Author | Helen Borrie |
Post date | 2003-05-30T01:55:13Z |
At 01:39 AM 30/05/2003 +0000, you wrote:
quoted identifiers - an option that is available to allow you to use
identifiers that contain spaces, or that need to be case-sensitive, or that
are the same word as a reserved word. IBManager might have decided to do
it this way automatically, if it detected that your legacy database had
such identifiers in place.
Really, its only usefulness is where you are migrating a database from
another RDBMS that permitted or required such things.
To correct it, you will have to rebuild your database *without* the quoted
identifiers, resolving any spaces or keywords. If you have some "illegal"
identifiers that you want to keep, it's OK to have a mixture of both quoted
and unquoted identifiers in your database, as long as you remember they are
there when you come to use them in queries...
heLen
>Hello!The reason is that you have used the option to create database objects with
>In my Database, this SQL is error:
>select * from tablename;
> it will cause a Table unknow error;
>This is all right:
>select * from "tablename";
>
>The same thing is happened in column name;
>I have to double quote every table name & column name in my SQL.
>
>My Enviroment:
>Firebird1.5 RC2 / Windows 2000.
>The database is created by EMS Interbase&Firebird Manager 3.
>
>What's the reason, and how to correct it?
quoted identifiers - an option that is available to allow you to use
identifiers that contain spaces, or that need to be case-sensitive, or that
are the same word as a reserved word. IBManager might have decided to do
it this way automatically, if it detected that your legacy database had
such identifiers in place.
Really, its only usefulness is where you are migrating a database from
another RDBMS that permitted or required such things.
To correct it, you will have to rebuild your database *without* the quoted
identifiers, resolving any spaces or keywords. If you have some "illegal"
identifiers that you want to keep, it's OK to have a mixture of both quoted
and unquoted identifiers in your database, as long as you remember they are
there when you come to use them in queries...
heLen