--- On Fri, 7/11/08, Eden Cardim <[EMAIL PROTECTED]> wrote: > <[EMAIL PROTECTED]> wrote: > > Because we use the resultset methods heavily, > particularly the pager. We'd have to find a minimal > subset of behavior we'd be willing to support and wrap > that in our our resultset wrapper. Yuck. > > I think you need DBIx::Class::Schema::RestrictWithObject
We already looked at that. As far as we can tell, it's just syntactic sugar for extra "where" conditions. It doesn't satisfy our requirement because we need to filter on conditions which cannot be expressed via SQL. So far, no one has been able to answer a very simple question: is it possible to build one resultset from another? Eden came close, but this is not a constraint which can be expressed via SQL. The filter criteria may have nothing to do with the database. We've found a frustrating work around, but frankly, it's a bit odd that this very simple question seems to be unanswerable. Cheers, Ovid -- Buy the book - http://www.oreilly.com/catalog/perlhks/ Tech blog - http://use.perl.org/~Ovid/journal/ Twitter - http://twitter.com/OvidPerl Official Perl 6 Wiki - http://www.perlfoundation.org/perl6 _______________________________________________ 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]
