At 07:34 PM 1/27/03 -0500, you wrote:
CLIP
I'm not sure why we are discussing the various implementations of rows in Oracle, ODBC, etc.
Not all database implementations necessarily have "rows"? Then why is there a revdb_querylist() function whose entire purpose is to fetch *all* of the rows? This just seems like technical misdirection here- this is about useability, not database implementations. There *could* be a revdb_currentrow() function, there just isn't. I just think it's worth implementing- I for one moved to a professional Rev license for one reason, and that is database support. RevDB is AWESOME. But I doubt this will be last time a database developer scratches his head when he can't fetch even the current row from a database cursor.
I can script around it- if others don't need this, then I guess I'm on my own.
Brian
I need it. Your not on your own. I don't have the Professional ver yet. Are you saying that the function(s) you are discussing are NOT in the 2.0 beta you have access to? If not then we need a little project to create a set of needed functions.
djl
|| Dave LeYanna ||
|| Director IS ||
|| Right to Life of Michigan ||
====================== _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
