croak 'must parse first' unless $self->_parsed;
$self->_make_objects unless $self->_objects;
- return wantarray ? @{ $self->_objects } : $self->_objects;
+ return $self->_objects;
}
sub errors {
0,
0]) unless $info_ok;
- # If header is given, there need to be a header for each profile
+ # If header is given, there needs to be a header for each profile
# and no empty headers.
if ($info_ok && $self->header) {
my @header = @{ $self->header };
# people insist that case sensitivity doesn't exist and try to enter all
# sorts of stuff. at this point we've got a profile (with keys that represent
# valid methods), and a header full of strings. if two of them match, the user
- # mopst likely meant that field, so rewrite the header
+ # most likely meant that field, so rewrite the header
if ($self->case_insensitive_header) {
die 'case_insensitive_header is only possible with profile' unless $self->profile;
if ($header) {
sub _check_multiplex_datatype_position {
my ($self) = @_;
- return 1 if !$self->is_multiplexed; # ok if if not multiplexed
+ return 1 if !$self->is_multiplexed; # ok if not multiplexed
my @positions = map { firstidx { 'datatype' eq lc($_) } @{ $_ } } @{ $self->header };
my $first_pos = $positions[0];
my $row = $self->_csv->getline($self->_io);
if ($row) {
my $header = $self->_header_by_row($row);
+ if (!$header) {
+ push @errors, [
+ 0,
+ "Cannot get header for row. Maybe row name and datatype field not matching.",
+ 0,
+ 0];
+ last;
+ }
my %hr;
@hr{@{ $header }} = @$row;
push @data, \%hr;
my $status = $csv->parse;
my $hrefs = $csv->get_data;
- my @objects = $csv->get_objects;
+ my $objects = $csv->get_objects;
my @errors = $csv->errors;
See Synopsis.
-Text::CSV offeres already good functions to get lines out of a csv file, but in
-most cases you will want those line to be parsed into hashes or even objects,
+Text::CSV already offers good functions to get lines out of a csv file, but in
+most cases you will want those lines to be parsed into hashes or even objects,
so this model just skips ahead and gives you objects.
Its basic assumptions are:
=item You do know what you expect to be in that csv file.
-This means first and foremost you have knowledge about encoding, number and
+This means first and foremost that you have knowledge about encoding, number and
date format, csv parameters such as quoting and separation characters. You also
know what content will be in that csv and what L<Rose::DB> is responsible for
it. You provide valid header columns and their mapping to the objects.
Parse the data into objects and return those.
-This method will return list or arrayref depending on context.
+This method will return an arrayref of all objects.
=item C<get_data>
In this case C<listprice_as_number> will be used to read in values from the
C<listprice> column.
-In case of a One-To-One relationsship these can also be set over
-relationsships by sparating the steps with a dot (C<.>). This will work:
+In case of a One-To-One relationship these can also be set over
+relationships by separating the steps with a dot (C<.>). This will work:
[ {profile => { customer => 'customer.name' }} ]