Re: Mixed Case Fields and SQL

["Steve Richter" <stephenrichter@xxxxxxxxx>]

On Dec 22, 2007 1:25 AM, Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx> wrote:

> Please note that this is the same behavior for Oracle, and is consistent
> with the SQL specification.  The specific paragraph for it is here,
> although
> you may need to read it in context to see how it forces your hand:
>
> "From SQL-92/Sec. 5.2:
> =======================================
> 10)The <identifier body> of a <regular identifier> is equivalent
> to an <identifier body> in which every letter that is a lower-
> case letter is replaced by the equivalent upper-case letter
> or letters. This treatment includes determination of equiva-
> lence, representation in the Information and Definition Schemas,
> representation in the diagnostics area, and similar uses."
>
> You CAN create column names with special characters, including lower-case
> letters, but they must then be enclosed in double quotes for eternity.
>
> The only major database where the column name is case sensitive by default
> is SQL Server.  As usual, the discrepancy is due to SQL Server not
> following
> the standards.


I have been curious lately how portable my as400 sql procedure code is to
other platforms like Oracle and sql server. In this instance it looks like
sql server would have no trouble creating mono case as400 sql procedures.
Having the option to write either portable, monocase code or more functional
and readable mixed case non portable procedures is what I prefer.  An
advantage to column names being mixed case is that your database integrates
better with the other programming languages you use on your platform. LINQ (
language integrated query ) in .NET is showing how functional this
integration can be.

-Steve