Greg wrote:
Well, I'm sorry to tell you this, but this is exactly what is done in the real world and in every database that allows you to create a case-insensitive index, there simply isn't another way to do it.1) nonsense -- assuming you can just store data in upper or lower case does not fly in "the real world".
Some databases may give you some sugar-coated way of doing it, but they all do it this way.
In case you misunderstood me, I was not suggesting that you only store the uppercase version of the value, but rather that you store an uppercase *copy*, so youl'd have both foo and upper_foo columns.
This is not nonsense, what if you know for a fact that there will be only 100 rows in that table?2) nonsense -- assuming that wrapping an upper() or lower() around an sql search causes a full table scan
MySql
*ROTFL*
My god, what have you been smoking kid?is case-insensitive and hopefully getting subselects in v4.1 coming soon so I'll try my luck with that, unless SAPDB is about to release soon that fixes this critical omission.
When you started talking about 'real world' I assumed that you meant real databases, not some toy like mysql.
I guess what I'm saying is: "If you think mysql isn't garbage, then you don't know the first thing about what databases are good for and you should probably just keep using mysql".
--
Regards Flemming Frandsen - http://dion.swamp.dk
PartyTicket.Net co founder & Yet Another Perl Hacker
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
