[Gambas-user] RE: Database Field Names

[Patrick JACQUOT]

GuruLounge - MailLists wrote:

>If you're stuck with lowercase in field names you could always get a
>little bit creative and try to store the field names in an optional
>field the keeps the case.  Maybe even create a separate table just for
>field names and create unique field names based on that.
>
>Might be a b*tch for search and the like but it could be a work-around.
>
>HTH,
>Jeff
>
>On Wed, 2006-04-19 at 08:55 +0100, Timothy Marshal-Nichols wrote:
>  
>
>>Thanks. I was a bit annoyed when I sent that email. I have charmed down now.
>>
>>First thoughts. How about:
>>
>>1.	Send the field name to the database in the case entered by the user.
>>2.	Before the field name is sent to the database check the name is unique in
>>the table with a case insensitive test. Do not allow field names that fail
>>the case insensitive test.
>>
>>Thanks
>>
>>8-{)} Timothy Marshal-Nichols
>><mailto: timothy.marshal-nichols at ...247...>
>>
>>
>>    
>>
>
>  
>
AFAIK the case-insensitiveness of field names (and table names) is 
required by the SQL standard.
Some SGBD allow case sensitiveness by various means
e.g. in PostgreSQL when the name is enclosed in double quotes

--
Patrick