The database features of Rev are very fast. Although I am not totally
conversant of all that goes on inside RevDB itself (as I use Trevor's
DB abstraction library to make RevDB easier to implement), or what
code you saw that looped but I know that using that library I can get
back the data as an array, or a block of binary or text, or as a
single character. No looping required. SQL calls are very powerful
and you can tell it to format the data any way you want before it
hits Rev. You could easily make an SQL terminal in rev in about an
hour. Others here (Sarah?) have made some excellent RevDB demo stacks
you can use right away.
Forgive the noob question:
At first glance it appears that accessing a database with Rev "hits"
the database for every column in every record in the repeat loop.
Whereas it seems that a SELECT query executed from, say, PHP, puts
all the data returned into an array in one query, then the data can
be extracted from the array in memory as needed.
Does Rev put a greater load on the database than a single PHP SELECT query?
(Or does is the PHP SELECT query kind of like a loop that has to
"hit" every column of every record anyway?)
--
stephen barncard
s a n f r a n c i s c o
- - - - - - - - - - - -
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
