On Sat, Feb 01, 2014 at 05:19:12PM +0100, Niels Thykier wrote: > File "/srv/ftp-master.debian.org/dak/dak/process_policy.py", line 136, > in binary_component_func > .join(Component).one() > File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/query.py", line > 2193, in one > "Multiple rows were found for one()") > MultipleResultsFound: Multiple rows were found for one() The program was expecting only one row but there was more than one there in the database. I personally don't like one() for this reason.
Checking the count and/or using first() is usually better, unless this is pointing to something else breaking (e.g. the thing that let the database have duplicate rows in the first place.) > (assuming you haven't implemented it already) Indeed. Not really the uploaders fault though, to answer his question. - Craig -- Craig Small (@smallsees) http://enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint: 5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140202215456.ga4...@enc.com.au
