At 12:02 PM 2/1/2006, Mathieu Dumoulin wrote:
This is more a "How would you do it" than a "How can i do it" question.
Didn't have time to try it, but i want to know how mysql_seek_row acts
with large result sets.
For example im thinking of building a node tree application that can have
dual direction links to nodes attached to different places.
I was wondering if i could actually have two result sets that query
everything sorted by ID (Links and Nodes) then just seek the rows i need
instead of dumping everything in php memory. When i mean large i mean
really large, more than the standard possible 2 mbs of data allowed by
most php servers.
That's where the "how you'd do it" comes into play. I think i'd just query
my tables, loop them but keep only the line (to do a data_seek later on)
and ID in some kind of an hash table or simply an array. This would make
it relatively fast without taking too much memory.
This is my solution, how do you people see it without dumping everything
to memory or by making recursive SQL calls (which will obviously slow
everything down i'm pretty sure)
Mathieu Dumoulin
Programmer analyst in web solutions
mdumoulin@xxxxxxxxxxxxxxx
I don't get it - what are you trying to do? Why? What is being visualized
in the tree structure?
Building trees is expensive, you're essentially duplicating the index of
the database, and if you fetch the data it's in memory regardless of how
you present it.
The mysql_data_seek needs the row number - but by then you're on the
client side, if this is to respond to a link.
Maybe I just don't see it - or maybe you're confusing server side and
client side.
Regards - Miles Thompson
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.1.375 / Virus Database: 267.14.25/247 - Release Date: 1/31/2006
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
