<html>
At 03:20 PM 1/27/03 -0500, you wrote:<br>
<blockquote type=cite class=cite cite><font face="arial" size=2>This is
all well and good, but every database that RevDB supports does have
rows.</font></blockquote><br>
Not necessarily true? Rev supports all systems that have an ODBC driver.
That would include the OODBs that I mentioned.<br><br>
You do, however have a significant point. Perhaps someone has developed a
set of generic scripts to handle the problem. I would have to go down
that path myself if a solution is not forthcoming. Perhaps in
2.0?<br><br>
djl<br><br>
<br>
<blockquote type=cite class=cite cite><font face="arial" size=2>What
confounds me is that RevDB has an API to fetch columns, but not rows. It
seems arbitrary, and less useful to me. Of course I may be missing
something, but I'm still not seeing what that is! Even if there were a
function to fetch *all* of the columns, that would seem like a step in
the right direction.<br><br>
Brian<br><br>
<blockquote type=cite class=cite cite>Might it have something to do with
SQL not really having a native concept<br>
of "rows"? SQL is a Query system not a
database<br>
management system. SQL can be used against an "Object
Oriented"<br>
database system even, which is somewhat different than the<br>
column,row,table paradigm we are used to when we generally talk
about<br>
databases. SQL is concerned about querying a database not
implementing<br>
it. It is up to the development environment you are in to do that<br>
(REVdb?).</blockquote><br>
</blockquote>
<x-sigsep><p></x-sigsep>
======================<br>
|| Dave
LeYanna
||<br>
|| Director
IS
||<br>
|| Right to Life of Michigan ||<br>
======================</font></html>