in reply to Re^5: Best complex structure?
in thread Best complex structure?

For the moment I don't use fetchall_arrayref (even it is a better solution) because some strange errors concerning the validity of my SQL occurs. anyway I am trying to build my structure.
@structure = ( [{ ... }, ], [ { ... }, { ... }, ], [ { ... }, { ... }, ], [ { ... }, { ... }, ], ); ## foreach @query { my @ex = executeRequest ($_); push @structure, []; for (my $i=0;$i<=$#ex;$i++) { push @structure->[$i], $ex[$i]; }
and I got this message:
Type of arg 1 to push must be array (not array element) at service.pm line 152, near "];"
I am a bit confusing with some notation of references and I think I don't interpret properly @results->[$i]. is there another one (except @results[$i]) ?
by the way, the sum function seems very interesting and I tested it.
my @structure = ( [ # Result from first query. { 'field1_statement1' => 'value', 'field2_statement1' => 'value' }, ], [ #Results from second query { 'field1_statement2' => 'value', 'field2_statement2' => 'value', 'field3_statement2' => 'value' }, { 'field1_statement2' => 'value', 'field2_statement2' => 'value', 'field3_statement2' => 'value' } ], [ # results from third query { 'field1_statement2' => 'value' } ] ); my $q2Total = sum @{ $structure[ 1 ] }; print $q2Total."\n";
and the results is ... 277446212

I do think I missed something :)
Sorry for these naive questions.

Replies are listed 'Best First'.
Re^7: Best complex structure?
by BrowserUk (Patriarch) on Jun 09, 2005 at 18:59 UTC

    Instead of

    push @structure->[$i], $ex[$i];

    You need

    push @{ $structure->[$i] }, $ex[$i];

    Which reads as; Use the $ith element of the array pointed at by the reference in the variable $structure as an array reference and then push the value of $ex[$i] onto that array.

    The basic form is that in ?{ $ref }, that if $ref contains a reference to an aggregate datastructure (array or hash) then ?{ $ref }, where ? is either @ or %, allows you to use that data structure. (Hmm. That probably doesn't clarify anything!)

    If $ref is an array ref, then @{ $ref } is the array it's referencing. Like wise for hashrefs and %{ $ref }.

    There are shortcut versions of this syntax. If the reference is a simple scalar then you can omit the curlies: @$ref, but when the reference is itself a member of an aggregate, that doesn't work. I tend to use the full @{ $ref } syntax always. For both consistancy and because I don't have to remember when the shortcur does and doesn't work.

    To get a better understanding of using references see perlreftut, perdsc and/or do a Super Search for "Tutorials references" here at PM.

    Sorry for these naive questions.

    Don't be. Leastwise, not for my sake. The only people who get upset about naive questions are those that either a) received their knowledge as a result of genetic imprinting; b) have forgotten that they once didn't know what they now know.

    In either case, it's just intellectual snobbery--the very worst kind.


    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
    "Science is about questioning the status quo. Questioning authority".
    The "good enough" maybe good enough for the now, and perfection maybe unobtainable, but that should not preclude us from striving for perfection, when time, circumstance or desire allow.
      Thanks for that!
      Your explanation is clear and  push @{ $structure->[$i] }, $ex[$i]; In my case, I found this solution, because $structure is not declared.
      push @structure , []; for (my $i=0;$i<= $#ex; $i++) { push @{ @structure->[$j]}, $ex[$i]; }
      now I am looping the structure like that
      foreach my $lev1 (@structure) { my $cnt = scalar(@{$lev1}; foreach my $lev2 (@{$lev1}) { my %hash = %{$lev2}; foreach my $key ( keys %hash ) { # if ($key eq $xx) etc. } } }
      Is there a way more straigthforward to fetch the key and the value? maybe wih the map function
        In my case, I found this solution, because $structure is not declared.

        Ah! That means you do not have strict and warnings enabled in your code?

        Whilst it is fine to ask naive questions (at least once and maybe even twice :), not using strict and warnings is unacceptable when you are asking for help.

        Why? Because each time you find a problem, and post code asking for help, the first thing I (and most others) are going to do is add strict and warnings and run perl -c yourscript in order to let the compiler tell us what errors you are making. Then we would have to post a reply pointing these problem out to you.

        Why should we do this, when the compiler can tell you about your mistakes directly?

        The compiler may seem pedantic and complain about a lot of things that you seem to be able to get away with by ignoring them, but each of those warnings is there for a very good reason: That of helping you write better code.

        If you choose to not use strict and warnings, you are effectively saying that you know better than the compiler. In which case, you don't need my help, because I always let the compiler point out my errors.

        This code

        push @structure , []; for (my $i=0;$i<= $#ex; $i++) { push @{ @structure->[$j]}, $ex[$i]; }

        Produces a warning. But more importantly, demonstrates that you are misunderstanding something quite important. Enabling warnings and working out how to stop that warning being produced will force you to become aware of that misunderstanding. It is much better that you do this now, before you misunderstanding becomes a long term habit that will continue to bite you each time you make it.


        Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
        Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
        "Science is about questioning the status quo. Questioning authority".
        The "good enough" maybe good enough for the now, and perfection maybe unobtainable, but that should not preclude us from striving for perfection, when time, circumstance or desire allow.