<HTML><FONT FACE=arial,helvetica><FONT COLOR="#000000" FACE="Geneva" FAMILY="SANSSERIF" SIZE="2">This is all well and good, but every database that RevDB supports does have rows.<BR>
<BR>
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 CITE STYLE="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px" TYPE="CITE"></FONT><FONT COLOR="#000000" FACE="Geneva" FAMILY="SANSSERIF" SIZE="2">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?).<BR>
</BLOCKQUOTE></FONT><FONT COLOR="#000000" FACE="Geneva" FAMILY="SANSSERIF" SIZE="2"><BR>
<BR>
</FONT><FONT COLOR="#000000" FACE="Geneva" FAMILY="SANSSERIF" SIZE="2"></FONT></HTML>