It seems to me that your database design (or the name of the 'id' column) is broken if you have non-unique ID's.
As for supporting this in the module: I'm not inclined to support something in DBIx::Simple that makes the value type returned dependent on the contents of the result set. That results in rather fragile code. You could just add a method, though:
# untested
package DBIx::Simple::Result::Metaperl;
our @ISA = qw(DBIx::Simple::Result);
sub map_arrays_of_hashes {
my ($self, $column_name) = @_;
my %arrays;
for my $row ($self->hashes) {
push @{ $arrays{$row->{id}} }, $row;
}
return wantarray ? %arrays : \%arrays;
}
...
$db->result_class = 'DBIx::Simple::Result::Metaperl';
my %arrays_of_hashes = $db->query(...)->map_arrays_of_hashes('id');
To keep DBIx::Simple simple, I'm not adding a proliferation of variants; a vast number map_foos_of_bars permutations could be thought of and I'm sure there's they could all be useful in someone's code somewhere, but let's draw a line... :)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Outside of code tags, you may need to use entities for some characters:
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
|
|