Re: Re: Speed of Template

Right now, in regards to fetchrow_array vs fetchrow_hashset, I've found that in the past versions of my code, I've been burned by using _array; when I did this part of the db query, I'd want the entire row of data, so I'd just select *, and when down the road the db changed because I added another column or the like, I had to go back and account for this aspect at all times. (I did need only specific elements for a quick lookup, but I put all of these into a utility module for the CGI). With how I've got it now, there's only one place where I need to call this key SQL statement, and thus I might be able to clean up the code enough to use _arrry vs _hashset.

The other reason that I'd want _hashset is that I'd like to toss some more things into the hash that I get back from it after the db, and as such, I can just take that hash ref from this call and not worrying about creating a new hash until the next row.

But again, it comes down to the fact that running a query with 1-5 results seems to take as long as a 1000 result one based on how my code is called, so I very much doubt the DB is the bottle neck, and instead Template being the problem. I've made sure to put the template calls outside of the loop (that is, make an array of the hashrefs from above, then let Template handle the for-next'ing it). From chormatic's post, it also suggests that caching of the templates should be going on if the envirnoment is persistent -- while I've folled the mod_perl docs and the like to modify the Apache conf, I don't have an easy way to test if I have created the right persistent environment.

Comment on Re: Re: Speed of Template

Replies are listed 'Best First'.
Re: Re: Re: Speed of Template by arturo (Vicar) on Feb 09, 2001 at 20:58 UTC
As far as getting the column titles out correctly goes, I'd suggest something along the lines of putting as much of your DBI stuff in a single module (an OO one if you like) as possible. That allows you to 'encapsulate' (love that buzzword) your database code. In that module, or elsewhere, you could use the `constant` pragma to alias column numbers to memorable tags. You'd only have one place you'd have to change, and you'd get the speed advantages of `fetchrow_array` over `fetchrow_hash`. e.g. : `use constant NAME => 2; use constant ID => 0; # ... my @row = $sth->fetchrow_array; print "Hi, Bob!\n" if $row[NAME] = 'Robert';` [download] Or some such. Just a thought. Philosophy can be made out of anything. Or less -- Jerry A. Fodor	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re: Re: Re: Speed of Template
by arturo (Vicar) on Feb 09, 2001 at 20:58 UTC

As far as getting the column titles out correctly goes, I'd suggest something along the lines of putting as much of your DBI stuff in a single module (an OO one if you like) as possible. That allows you to 'encapsulate' (love that buzzword) your database code. In that module, or elsewhere, you could use the constant pragma to alias column numbers to memorable tags. You'd only have one place you'd have to change, and you'd get the speed advantages of fetchrow_array over fetchrow_hash.

e.g. :

use constant NAME => 2;
use constant ID => 0;
# ...

my @row = $sth->fetchrow_array;
print "Hi, Bob!\n" if $row[NAME] = 'Robert';
[download]

Or some such. Just a thought.

Philosophy can be made out of anything. Or less -- Jerry A. Fodor

[reply]
[d/l]
[select]