Subject | Re: [firebird-support] double single quote |
---|---|
Author | Martijn Tonies |
Post date | 2004-03-17T17:05:49Z |
Hi,
use for any future projects).
When using identifiers, only use double quotes if you want them
to become case sensitive, including non-identifier characters or
using reserved words.
eg: SELECT * FROM "TABLE"
(which is rather stupid of course)
Use single quotes around strings:
WHERE MyCol = 'test'
And escape a single quote inside a string with another single
quote:
WHERE MyCol = 'O''Conner' (these are two single quotes)
With regards,
Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com
> Can someone explain me what is the rule in using single or doubleAssuming "dialect 3" (the newer dialect which you should
> quotes?
>
> It seems that double quote works if you use it in a field or table
> name but doesn't work in where clause for values. And the Single
> quote is the opposite.
>
> I'm just curious if this is done on purpose for SQL compliance or just
> a current limitation.
>
> I came across this problem when converted some old simple SQLS that
> worked in Oracle (which supports just about everything including
> apples and bananas) and now doesn't work in Firebird.
>
> It's not really a request, but more for learning purpose and personal
> documentation. I don't want Firebird to be a monster like Oracle, I
> like its simplicity.
use for any future projects).
When using identifiers, only use double quotes if you want them
to become case sensitive, including non-identifier characters or
using reserved words.
eg: SELECT * FROM "TABLE"
(which is rather stupid of course)
Use single quotes around strings:
WHERE MyCol = 'test'
And escape a single quote inside a string with another single
quote:
WHERE MyCol = 'O''Conner' (these are two single quotes)
With regards,
Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com