Hi Art, Unicon ODBC interface was written in 1999 if I remeber... At that time the main developement was tested against MySQL using MyODBC version 2.x. The ODBC implementation then is ODBC 2.x compatible but myODBC did not offer any cursor facility so things like positioned operations were not available. So the only way to update or delete a row is actually to write a query using sql(). The concept of client or server cursor is not available at this moment, which means that the only way to work on the database is to send SQL queries to the server and if these return a dataset there's only a unidirectional sequential way to read it (fetch()).
Ciao, Federico Federico Balbi Division of Computer Science University of Texas at San Antonio 6900 N. Loop 1604 West San Antonio, TX 78249-0667 [EMAIL PROTECTED] http://www.cs.utsa.edu/~fbalbi On Sun, 31 Aug 2003, Art Eschenlauer wrote: > Sorry about the subject, I couldn't resist. > > Unicon defines the sql( db, sqlstring ) function that initializes a > cursor for an ODBC db such that subsequent fetch( db ) produce rows > meeting the criteria specified by sqlstring. > > My question is this: for databases that support server-side cursors, PHP > and MS Access permit you to specify whether a client-side or server-side > cursor is used. Does Unicon: > * use server-side cursors by default if available? > * rely upon implicit (presumably server-side) cursors? > * do something else not listed here? > > I "read the fine source code" (rtfsc) but did not find that the answer > to my question leapt out at me. > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Unicon-group mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unicon-group
