This is all well and good, but every database that RevDB supports does have rows.
Not necessarily true? Rev supports all systems that have an ODBC driver. That would include the OODBs that I mentioned.
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?
djl
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.
Brian
Might it have something to do with SQL not really having a native concept
of "rows"? SQL is a Query system not a database
management system. SQL can be used against an "Object Oriented"
database system even, which is somewhat different than the
column,row,table paradigm we are used to when we generally talk about
databases. SQL is concerned about querying a database not implementing
it. It is up to the development environment you are in to do that
(REVdb?).
|| Dave LeYanna ||
|| Director IS ||
|| Right to Life of Michigan ||
====================== _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
