Re: dbix::class find() question

poj is right already but I offer the other path–

my $rs = $schema->resultset('records');
my @records = $rs->search({ id => \@ids });
[download]

The only caveat I might offer here is that search won’t explicitly complain or fail if say only one of the ids is found. I would also suggest that you do this kind of thing instead–

my $rs = $schema->resultset('records')
    ->search({ id => \@ids });
for my $row ( $rs->all ) {}
[download]

As long as you remain in the realm of pure resultsets you don’t execute SQL. So working with them that way—RS until you are ready for records—is more flexible, extensible, and often more performant—as the biz-devs say—since you can end up hitting the DB less.

Update! Didn’t use hasref args initially.

Comment on Re: dbix::class find() question Select or Download Code

Replies are listed 'Best First'.
Re^2: dbix::class find() question by tqisjim (Beadle) on Jan 18, 2016 at 19:58 UTC
is that statement equivalent to this? `$rs = $schema->resultset('records') ->search({ id => { in => \@ids } }) ;` [download] The syntax in your example is a definite improvement!	[reply] [d/l]
Re^3: dbix::class find() question by Mr. Muskrat (Canon) on Jan 18, 2016 at 20:42 UTC
Sort of. The queries are different but what they return should be the same. # based on the usual DBIC example tables my @ids = (1..4); my $rs = $schema->resultset('Cd') ->search({ cd_id => \@ids }); warn "query: ", ${$rs->as_query()}->[0], "\n"; $rs = $schema->resultset('Cd') ->search({ cd_id => { in => \@ids } }); warn "query: ", ${$rs->as_query()}->[0], "\n"; __END__ query: (SELECT me.cdid, me.artistid, me.title, me.year FROM cd me WHER +E ( ( cd_id = ? OR cd_id = ? OR cd_id = ? OR cd_id = ? ) )) query: (SELECT me.cdid, me.artistid, me.title, me.year FROM cd me WHER +E ( cd_id IN ( ?, ?, ?, ? ) )) [download]	[reply] [d/l]
Re^4: dbix::class find() question by Your Mother (Archbishop) on Jan 18, 2016 at 21:41 UTC
Very nice++.	[reply]
Re^3: dbix::class find() question by Your Mother (Archbishop) on Jan 18, 2016 at 20:29 UTC
Yeppers (but see my syntax update). :P	[reply]