Bill Moseley wrote: > > > On Fri, May 7, 2010 at 7:25 AM, Ovid <[email protected] > <mailto:[email protected]>> wrote: > > --- On Fri, 7/5/10, Bill Moseley <[email protected] > <mailto:[email protected]>> wrote: > > > Still, I have wondered if DBIC should throw an exception if you > try and > > access a column that was not fetched from storage. > > I think that would be better than forgetting to check if the column > is loaded and getting a silent failure. Still, that would be a > backwards-incompatible change. > > > True. > > But, case in point: I'm using DBIx::Class::Ordered and it started to > fail today with a somewhat odd error. Turned out that "columns" had > been modified such that the position column was no longer returned in > the row. Ordered was assuming it was a NULL and tried to set the > position to a value that existed and the database complained that it was > not unique. >
I don't see the attached test case so we can fix the bug in *Ordered* (by making sure we have the necessary info available before we start shuffling things around). _______________________________________________ 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]
