What George described is exactly how client-server is implemented using Borland's development products. The result set is "cached" locally on the client. Any updates performed on the client data set must be "applied" to the server. All aspects of the entire process are controlled by the developer.
Normally, an update cycle would be: Select the data set, close the database, update the local data set, open the database, apply updates with error handling, close the database. All opening and closing of the database is optional based on the environment and design constraints. As far as I know that is the basic "industry standard" design for Client-Server. Fred > -----Original Message----- > From: Tito Ciuro [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 19, 2004 1:35 AM > To: George Ionescu > Cc: Sqlite Forum > Subject: Re: [sqlite] Re: Life of a cursor > > > Hello George, > > > After that, it's of no use to keep the database open, so it closes it. > > And sends the results obtained back to the client. > > Wow! This is the first I hear that. Wouldn't that be an expensive > operation? (opening, closing, reopening...) > ... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
