Florian Boesch wrote:
No I don't agree that this is a fixed bug.
Sorry, I don't understand what you are referring to (I haven't mentioned a bug fix).
But I was looking through the timeline to find any bugs that referred to this issue and I see that there is now a selectfirst() and its partner selectfirst_by() which have the required contract of returning None if no rows are found and the first if > 1 are found - see http://www.sqlalchemy.org/trac/changeset/1136 for a doco change.
In that light selectone() is behaving as per contract and if that isn't the required contract for that piece of code then selectfirst() would be the go.
HTH Robert ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
