Yes, I was thinking a very simple stub ResultSet class for every Result
source. Something like:
package MyApp::Schema::ResultSet::MyTable;
use strict;
use warnings;
use base 'DBIx::Class::ResultSet';
# example
#sub get_by_id {
# my $self = shift;
# my $id = shift;
#
# return $self->find($id)->all;
#}
1;
In practice, it may be overkill to create a ResultSet class for each
Result class, and admittedly it's not too difficult to create these
ResultSet classes by just doing one and copying as needed. I'm probably
being lazier than I should be...
jarom smith
tech go-to guy
J. Shirley wrote:
On Wed, May 27, 2009 at 5:31 PM, Jarom Smith <[email protected]
<mailto:[email protected]>> wrote:
Sorry, one more question (and this one does have to do with Catalyst
more than DBIC, I think...)
Is there any magical invocation for the create script which will
make a bunch of stub ResultSet classes for me, similar to how the
Result classes are auto-generated when I do
script/myapp_create.pl model MyAppDB DBIC::Schema MyApp::Schema
create=static components=TimeStamp,EncodedColumn dbi:mysql:myapp
'dbuser' 's3kr1t' '{ AutoCommit => 1 }'
? (and if so, what is it?)
thanks,
jarom smith
tech go-to guy
What do you want/expect the resultset classes to contain? Or do you
want a resultset class created for every result source?
I've found that using a custom resultset default via load_namespaces
suits most of my needs, but I'd be interested to hear other scenarios.
Thanks,
-J
------------------------------------------------------------------------
_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
