Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #77316
| From | dieter <dieter@handshake.de> |
|---|---|
| Subject | Re: Keeping python code and database in sync |
| Date | 2014-08-30 08:36 +0200 |
| References | <ltpseg$p9m$1@ger.gmane.org> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.13642.1409380579.18130.python-list@python.org> (permalink) |
"Frank Millman" <frank@chagford.com> writes: > ... > It is a simple matter to write a program that updates the database > automatically. The question is, what should trigger such an update? My first > thought is to use a version number - store a version number in the working > directory, and have a matching number in the code. If someone downloads the > latest version, the numbers will no longer match, and I can run the upgrade > program. > > The problem with that is that version numbers are usually reserved for > tagged releases, but this could happen as the result of any commit in the > current development cycle. I use "data model version number"s for this. They identify the data model version and are idenpendent of any program version number. Such a version number is changed whenever the data model changes (and there is the need for a model upgrade).
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Keeping python code and database in sync dieter <dieter@handshake.de> - 2014-08-30 08:36 +0200
csiph-web