Re^2: OT: benefits of database normalization

"Also, btw, both "name" and "type" are SQL reserved words and should not be used as column names unless they are quoted."

Not true, at least not true to all database implementation. I just tried this in Oracle, and it worked with no problem:

create table temp(type number(1), name number(1))
[download]

Comment on Re^2: OT: benefits of database normalization Download Code

Replies are listed 'Best First'.
Re^3: OT: benefits of database normalization by jZed (Prior) on Oct 03, 2004 at 05:10 UTC
The fact that Oracle lets you get away with using those doesn't mean that it is a good idea to use them anymore than the fact that MSIE lets you get away with sloppy HTML means that you should write sloppy HTML. If there's any chance that the schema will be ported to another RDBMS in the future (and the OP is asking questions about the long range), then it is better to avoid ISO/ANSI SQL reserved words. Another reason to avoid them is if the schema will be used with parsing, cataloging, or validating software which may or may not recognize them.	[reply]

Replies are listed 'Best First'.

Re^3: OT: benefits of database normalization
by jZed (Prior) on Oct 03, 2004 at 05:10 UTC

The fact that Oracle lets you get away with using those doesn't mean that it is a good idea to use them anymore than the fact that MSIE lets you get away with sloppy HTML means that you should write sloppy HTML. If there's any chance that the schema will be ported to another RDBMS in the future (and the OP is asking questions about the long range), then it is better to avoid ISO/ANSI SQL reserved words. Another reason to avoid them is if the schema will be used with parsing, cataloging, or validating software which may or may not recognize them.

[reply]