in reply to Re: Template Toolkit - passing hashes
in thread Template Toolkit - passing hashes

Thanks.

Another problem is that you are building a hash of hashes, but your template seems to expect a list of hashes.

But I thought:
http://www.template-toolkit.org/docs/plain/Manual/Variables.html#Hash_Array_References

Members of hash arrays are accessed by specifying the hash reference a +nd key separated by the dot '.' operator. my $vars = { 'home' => 'http://www.myserver.com/homepage.html', 'page' => { 'this' => 'mypage.html', 'next' => 'nextpage.html', 'prev' => 'prevpage.html', }, }; template: <a href="[% home %]">Home</a> <a href="[% page.prev %]">Previous Page</a> <a href="[% page.next %]">Next Page</a>




Forget that fear of gravity,
Get a little savagery in your life.

Replies are listed 'Best First'.
Re^3: Template Toolkit - passing hashes
by polettix (Vicar) on Apr 02, 2007 at 14:06 UTC
    You're not reproducing the same setup. Instead of:
    Call list for [% today %] <p> [% FOREACH user IN data %] Be sure to call [% user.ulname %], [% user.ufname %] [% END %]
    you should use the values virtual method:
    Call list for [% today %] <p> [% FOREACH user IN data.values %] Be sure to call [% user.ulname %], [% user.ufname %] [% END %]
    which gives you back the list that FOREACH iterates on.

    As an alternative, you should modify your Perl code:

    # build data structure my @data; while (($user_id, $ufname, $ulname) = $sth->fetchrow_array()) { push @data, { ufname => $ufname, ulname => $ulname } }
    and then pass \@data instead of \%data.

    Which way to go is up to you, but keep in mind that using the hash will destroy record order (which does not seem an issue in your case, you don't specify any ORDER BY clause in your SQL query) and using an array won't let you address every record by user_id. Just to name a few differences.

    Flavio
    perl -ple'$_=reverse' <<<ti.xittelop@oivalf

    Don't fool yourself.