UBB.Developers Forums UBB.threads 6 Bug Reports Scream

I'm finding it kind of weird how you keep db connections open and keep grabbing results from it..

Is it because you are trying to take up the least amount of memory on the server as you can?

It seems to be part of the reason why I can't get postgres to work.. PHP likes to print out an error message any time you try to grab a row that doesn't exist.... which tends to happen using your method of grabing the next row (having a count var that increments it's self etc..)

How I usually do it is store all of the results in a disconnected recordset..

Usually what I do (in perl) is have a while statement that grabs a hashref for each row and embeds it into an array, and then I return a reference to that array..

so then you can access the results like:
print $$table_ref[0]{NAME};


Here's some example code of how I do it in perl (and it works very well)

You create a method that looks like this:
sub get {

my ($query) = @_;

my (@return);

my $rs = $DB->do ( $query );


while ( my $data = $rs->fetchrow_hashref() ) {

push @return, { %$data };

} # End: while


$rs->finish();

return ( \@return );

} # End: get



And then to do a query you do this:

$table_ref = $dbh->get ( "select name, pass from user" );

foreach my $tmp ( @$table_ref ) {

$name = $tmp{NAME};
$pass = $tmp{PASS};

}

or:

$name = $tmp[0]{NAME};
$name2 = $tmp[1]{NAME};


This will create a db connection new query and get off the db as quick as possible, and then you just loop through the results.. you never *try* to grab a row that doesn't exist... (which happens a lot in the code you have now)

------------------------------------------------
Jeremy 'PeelBoy' Amberg