Frankly, I agree with Matt that search behavior really should be case insensitive. I've wanted to check out postgres for a while, but finding this out may well slow me down.
If, like most other dbs, searching for calculated expressions (LCASE(some_column) = 'foo' etc) is significantly inefficient, how are you supposed to manage this in the real world? Only idea I had was to store every possibly searchable value in mixed case for display, and somewhere else in all lowercase for searching. The other thing is that this makes it hard to use postgres as a drop-in replacement for most other common dbs. Sure, you could (re-)design the app from scratch to handle what most other dbs usually do automatically, but if that's really what you have to do, it seems like a much bigger decision than dealing with the much less pervasive syntax differences between vendors. Are folks really sure that no case-insensitive collation option is available? Dave ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create robust enterprise, web RIAs. Upgrade & integrate Adobe Coldfusion MX7 with Flex 2 http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:266513 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
