Strikes me we've got a number of sql_maker overrides that are purely to
change the class name now, so lets factor that out.

You mean like adding a DBIC::Storage::DBI->sql_maker_class() and providing a default DBIC::Storage::DBI->sql_maker() that instantiates that class?

Also, what other databases support FOR UPDATE ? Is it worth pushing that
one down to DBIC::SQL::Abstract itself ?

Hmm, no idea, but googling for SELECT FOR UPDATE, Oracle and Mysql popped up. Wasn't aware of these supporting SELECT FOR UPDATE.



--d

_______________________________________________
List: http://lists.rawmode.org/cgi-bin/mailman/listinfo/dbix-class
Wiki: http://dbix-class.shadowcatsystems.co.uk/
IRC: irc.perl.org#dbix-class
SVN: http://dev.catalyst.perl.org/repos/bast/trunk/DBIx-Class/
Searchable Archive: http://www.mail-archive.com/dbix-class@lists.rawmode.org/

Reply via email to