> >As a general thing, using double quotes on object names is a waste of
> >time. If you need to use a reserved word as a column or table or
> >procedure or view name, OK, that's a good reasons. If you need to use a
> >name with a space or a non-ascii character, OK, that's a good reason.
> >If you like typing double quotes everywhere, that's a reason but not one
> >that's going to please many of us who answer questions on this list.
> >
> >
> I like delimited identifiers because I'm used to the Pascal case
> notation when I work on the business tier (Java, C#, C++...) and I do
> not really like to use underscores... even if it is quite standard for
> database designers. But that's obviously a problem of personal taste.

If you don't use quotes, you still can write.

MyTable.MyColumn

while the DDL returned will be:

create table MYTABLE
(
MYCOLUMN integer
)

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server
Upscene Productions
http://www.upscene.com