Local database and updates
- From: "Peter Bernhardt" <peter@xxxxxxxxxxxxx>
- Date: Thu, 25 Aug 2005 08:19:14 -0700
I'm reviewing an application that uses a local database for a .NET
application. In adding logic to automatically update components of the
application (content files, assemblies updates, and data updates) I found
that the original design locks the database while the app is running. This
means that the updater code needs to detect a runnning instance of the .NET
app and signal it to close down before it can apply database updates. This
makes it impossible to apply updates automatically.
It seems to me that tightly linking the database to the .NET app is
unnecessary. I see no reason why the database cannot be updated while the
application is running. The updater itself could lock portions of the
database during updating to prevent corruption and then signal the
application to refresh its in-memory data once the updates have been
committed.
I'd appreciate any feedback from others about this issue as I want to be
sure that I've thought through all the possibilities.
TIA.
--
Peter Bernhardt
SharpSense Software LLC
peter@xxxxxxxxxxxxxxxxxxxx
.
- Prev by Date: Re: AutoStart
- Next by Date: Unable to back up database...
- Previous by thread: AutoStart
- Next by thread: Unable to back up database...
- Index(es):
Relevant Pages
|