Bill Moseley wrote:
Two issues I'd like to see discussed here is if DBIC should throw an exception if find() returns more than one row (instead of a warning), and if it makes sense to fall back to the full criteria passed to find() if no unique key can be determined.
I want to make sure I am getting this right - are you proposing that we discuss drastically changing a stable API, potentially breaking DBIC for hundreds if not thousands of users, all for the sake of correctness? I am still not sure what the discussion scope is, thus I'll reserve judgment until more details emerge. But if I was to guess what you actually need - I can propose extracting the "ooh you got too many rows" code into a single overridable point, so you can hook it in your base resultset and make it die, or do whatever else you wish it to do. So - MOAR DETAILS! :) _______________________________________________ List: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class IRC: irc.perl.org#dbix-class SVN: http://dev.catalyst.perl.org/repos/bast/DBIx-Class/ Searchable Archive: http://www.grokbase.com/group/[email protected]
