On Tue, 13 Jan 2009 15:21:16 +0900 wrote: > Having a *very* brief look at the code, it seems some work might need > to be done to separate the "paging" method out into DB specific > modules...
It's already handled by SQL::Abstract::Limit (and some hacks on top of that in DBIC::SQL::Abstract). > Does DBIC already use SQL::Abstract::Limit? It does. > Seems that has all the > appropriate logic in there, but DB support is based on a "you have to > read it list" rather than a specific module matching the DBD::module SQL::Abstract::Limit has an auto-detection mechanism that tries to determine the proper limit dialect and it is used by DBIC, but this auto-detection mechanism depends on the fact that the DBD itself knows which database it deals with. And in some cases (JDBC bridge, maybe ODBC) it does not know. In those cases you have to specify it manually in connect_info (see limit_dialect in DBIx::Class::Storage::DBI and SQL::Abstract::Limit). norbi _______________________________________________ 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]
