Hey guys. First off, thanks to all who have helped me in the recent weeks. We're in crunch on my project and my rather complicated server, combined with my lack of DB experience, has given me plenty of problems to deal with.
My core users table has a user defined by a string which is their name. This string is used to address many other tables relating to users. Not only is the primary key a string (which I understand is bad enough), but I also have to use LIKE rather than = because the high level language I use is a bit eccentric about case-ing. The time has come for me to sort out this problem, as it is negatively impacting the speed of almost every query I do, and the speed of these queries is definitely a problem. As there are hundreds of queries around my server codebase I would prefer not to have to change every single one to use a numeric id for a user rather than a string - but maybe this is the only real way of optimising this properly? I would appreciate any general advice about a solution to this which doesn't require refactoring every query, and if the opinion is that I do need to just bite the bullet and make every reference to a user in SQLite an integer, what would be the best way of going about this exactly. Thanks, Ian _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
