From: | Jordan Reiter <jordan(at)breezing(dot)com> |
---|---|
To: | Ian Barwick <barwick(at)gmx(dot)net>, Chris <csmith(at)squiz(dot)net>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Case Sensitive "WHERE" Clauses? |
Date: | 2002-09-27 00:17:35 |
Message-ID: | a05100306b9b9537533b5@[63.172.201.5] |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
> > > > Are string comparisons in postgresql case sensitive?
>> >
>> >Yes, unless you specify otherwise.
>> >
>> >Are you sure you are using the right database? I can
>> >reproduce similar results, but only like this:
>>
>> You're using MySQL in these examples .. not Postgres :)
>
>Full points for paying attention ;-)
>
>This, erm, characteristic of the former caused me a lot of grief once...
>
>Anyone know what the ANSI standard is? I don`t recall any other
>database apart from MySQL which default to case-insensitive
>CHAR or VARCHAR columns.
Microsoft Products (SQL Server, Access) are case-insensitive.
I find it hard to understand why it's advantageous that column names are NOT case sensitive, while field content is. You have a *lot* more control over the database columns than you do over the content that goes into the fields. In my opinion, allowing someone to refer to a column as first_name, First_Name, or FIRST_NAME just encourages bad programming.
--
Jordan Reiter mailto:jordan(at)breezing(dot)com
Breezing.com http://breezing.com
1106 West Main St phone:434.295.2050
Charlottesville, VA 22903 fax:603.843.6931
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2002-09-27 01:20:08 | Re: Passing array to PL/SQL and looping |
Previous Message | Jochem van Dieten | 2002-09-26 23:41:33 | Re: Case Sensitive "WHERE" Clauses? |