On Jan 23, 2006, at 5:41 PM, Michael Bayer wrote:
hmm does it really ? I am most accustomed to Oracle where getting just the first row back of a huge result set is not much different than just getting one (and also, Oracle doesnt even have 'limit', and I have instead hacked together some "rowid" type of thing that doesnt work very well, so the below code is not terrfiic for oracle).
at least for postgres it makes a big difference. i don't know what the root causes for that might be. i mostly have been using selectone() for interactive debugging where the delay was both noticeable and annoying (for me)...
Maybe I should make a parameter "optional_limit" or something which means, "use limit but only if the database likes it for smaller result sets".
not being familiar with a large number of dbs, i'm not sure what makes sense for this kind of thing - i can only say that it made a difference for me. thx,d ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Sqlalchemy-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
