thanks all for trying to help but both those answers offered by several people in this thread are complete nonsense for any real application.
1) nonsense -- assuming you can just store data in upper or lower case does not fly in "the real world". 2) nonsense -- assuming that wrapping an upper() or lower() around an sql search causes a full table scan SAPDB was looking very good/excellent in most other respects until I hit this showstopper. MySql 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. Also, I'd done some digging since the original post and SAPDB (and most other databases) also refer to case-sensitivity and collation as the same sort of thing. Thanks, Greg. "Flemming Frandsen" <[EMAIL PROTECTED]> wrote in message news:3DCB77F6.3080405@;partyticket.net... > Greg Matthews wrote: > > How do I make a SAPDB case-insensitive? > > What do you mean? > > If you mean: "How do I match a value case-insensitively?" > Then there are two answers: > > 1) Don't, store the uppercase or lowercase version of the value and > match that, this is good if you want to do large searches that need > to be indexed. > > 2) Simply do: "select * from foo where upper(bar)=?" this is slow > beause you can't index the bar column, so only use for small tables. > > -- > 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
