![]() |
aquery/aexecute question - Printable Version +- SphereCommunity (https://forum.spherecommunity.net) +-- Forum: Sphere 0.56d (/Forum-Sphere-0-56d) +--- Forum: General Help (/Forum-General-Help) +--- Thread: aquery/aexecute question (/Thread-aquery-aexecute-question) |
aquery/aexecute question - Rattlehead - 07-29-2013 04:06 PM ok, so i have a small procedure that simple checks my database to see if they have registered an email address, ill post it since i believe someone else was looking for somethign similiar: Code: on=@login super simple, if the cell is NULL, it brings up a dialog for them to put one in now, my question is this; will using a aquery instead of just the above make a difference in server performance? it seems i will have to write a bit more code for it to function the same, as aquery will need a function to call, basically what im asking is will it make any noticeable difference considering eventually the database will start to get big, or no? RE: aquery/aexecute question - Shaklaban - 07-29-2013 09:15 PM if you index your wb_acc_info table by username column it will run faster. also you need to use: db.query SELECT email FROM wb_acc_info WHERE username = '<account.name>' instead of using LIKE. AEXECUTE and AQUERY only useful for large data processing in background. RE: aquery/aexecute question - Rattlehead - 07-30-2013 03:39 AM yes, my table is indexed for the username column, and i used LIKE becus username is a string, and since = is technically a numeric expression and not made for comparing strings: 'Per the SQL standard, LIKE performs matching on a per-character basis, thus it can produce results different from the = comparison operator:' http://dev.mysql.com/doc/refman/5.0/en/string-comparison-functions.html you are right in saying that the = will be faster, but according to MySQL, LIKE compares strings more accuratly than using the = ![]() |