that i kind of counted on. if i have a column that i need to index i fix the case as i maintain the data, ill still have an unfixed column for the users view. that way i kind of compromise. Woody
--- On Fri, 7/25/08, D. Richard Hipp <[EMAIL PROTECTED]> wrote: From: D. Richard Hipp <[EMAIL PROTECTED]> Subject: Re: [sqlite] text datatype matching functions, binding vs explicit insert To: "General Discussion of SQLite Database" <sqlite-users@sqlite.org> Date: Friday, July 25, 2008, 7:50 PM On Jul 25, 2008, at 7:44 PM, Harold Wood & Meyuni Gani wrote: > But you can use where 'AA' = upper(fld1) = to get around case issues. Yes you can. But you need to be aware that doing so will prevent an index from being used to speed the search. If your table is small it shouldn't make any difference. But for a table with millions of entries, you could run into performance problems. D. Richard Hipp [EMAIL PROTECTED] _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
