On Monday, January 27, 2003, at 01:20  PM, [EMAIL PROTECTED] wrote:

This is all well and good, but every database that RevDB supports does have rows.

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.

Sorry, maybe I misunderstood. The client-side concept of rows, that is: rows of the query result set, I think is implemented by revdb's concept of cursors. see the revdb_move*, revdb_cursor*, revdb_query.


Alex Rice, Software Developer
Architectural Research Consultants, Inc.
[EMAIL PROTECTED]
[EMAIL PROTECTED]



_______________________________________________
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution


Reply via email to