deployment - How to go about catching database and software version mismatch on deployed application? -
I am developing a standalone application that accesses a common database on a server. This will be used by some dozen people in my organization.
I know that I will need to update the software and database design. This creates the likelihood that someone will do a query on the database using the old software.
I already have a system that tries to start the old version of the user. application. However, this is not against anybody who keeps the application for a long time.
My idea was to keep a version entry (tblVersion or something) in the database and check it every time but not just read it.
In this way, I can catch things that (I think) may be that (I think) record (except tblVersion) is added to any table in DB , Is updated or removed even if the user has the latest version of SW: Check the version in DB about what the code contains, and if there is no mismatch, then add, update or delete the operation Do not allow. At the same time, I do not add tblVersion to DB overhead of many checks.
My question: Is this the sound? Is there a better way to go about it? If so, then?
Thank you!
A new, inconsistent rollout of a person's use case app is open and database schema ( Or interpretation) is modified in a structurally consistent, but meaningfully incompatible methods seem very narrow.
A schemine table with two and two toplevels, the second with the last schematic version of the existing schema version, is the second most catchy case, while not seriously describing its application.
Checking on each writing will be a terrible disturbance, if you are really worried about the scenario, then the timer stops every hour or two which checks the table version and pops up a dialogue Does a warning to the user to get a new version.
Comments
Post a Comment