Hello Richard, Thursday, July 7, 2005, 1:16:29 AM, you wrote: RL> You've just made my point. RL> The actual data tuple returned in both cases is a long, if there RL> is a user to match. This is where we differ :) I don't believe MySQL will return an entire longs worth of data (typically 4 bytes) if the value is simply 1. By return I mean across the network, etc. But maybe that is blind faith in the skills of MySQLs developers? ;) RL> 99 times out of a hundred, the very next thing your application is RL> gonna do is get their ID, maybe their name, maybe their email, RL> etc, so you can do something more interesting in your script than RL> just know they exist. Sure. But in the example given this wasn't the use of the query - they were checking to see if the user existed so they could INSERT a new one. RL> Some days I think newbies should be forced to use IBM PC Jrs with RL> 16K RAM and a 60 Meg hard drive (or whatever) just so they learn RL> to code... :-) I dunno.. I've seen shit code on every single system I've ever come across :) Best regards, Richard Davey -- http://www.launchcode.co.uk - PHP Development Services "I do not fear computers. I fear the lack of them." - Isaac Asimov -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
