Hello again,
All these answers are client/server related and very informative, but the original question is still in the open. In SQLite's case, let's assume I want to make a wrapper which add some functionality and simplifies some features. I create a cursor which contains a copy of the data. If I close the database, is it the norm to expect the results to be still available? Some developers may want the cursor to be available, other may want to invalidate them...
Should I make it optional?
Thanks again,
-- Tito
On 19 may 2004, at 10:12, Fred Williams wrote:
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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
