Re: Keeping python code and database in sync

Path	csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.xs4all.nl!newsfeed4.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Return-Path	<python-python-list@m.gmane.org>
X-Original-To	python-list@python.org
Delivered-To	python-list@mail.python.org
X-Spam-Status	OK 0.029
X-Spam-Evidence	'H': 0.94; 'S': 0.00; 'subject:code': 0.07; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'changes': 0.15; 'received:80.91.229.3': 0.16; 'received:dip0.t-ipconnect.de': 0.16; 'received:plane.gmane.org': 0.16; 'received:t-ipconnect.de': 0.16; 'subject:python': 0.16; 'code.': 0.18; 'commit': 0.19; 'header:User-Agent:1': 0.23; 'question': 0.24; 'header:X-Complaints-To:1': 0.27; 'matching': 0.30; 'usually': 0.31; 'directory,': 0.31; 'releases,': 0.31; 'writes:': 0.31; 'this.': 0.32; 'run': 0.32; 'could': 0.34; 'problem': 0.35; 'but': 0.35; 'there': 0.35; 'version': 0.36; 'charset:us-ascii': 0.36; 'should': 0.36; 'version,': 0.38; 'to:addr:python-list': 0.38; 'to:addr:python.org': 0.39; 'changed': 0.39; 'received:org': 0.40; 'identify': 0.61; 'reserved': 0.61; 'numbers': 0.61; 'matter': 0.61; 'simple': 0.61; 'first': 0.61; 'received:217': 0.63; 'such': 0.63; 'happen': 0.63; 'latest': 0.67
X-Injected-Via-Gmane	http://gmane.org/
To	python-list@python.org
From	dieter <dieter@handshake.de>
Subject	Re: Keeping python code and database in sync
Date	Sat, 30 Aug 2014 08:36:04 +0200
References	<ltpseg$p9m$1@ger.gmane.org>
Mime-Version	1.0
Content-Type	text/plain; charset=us-ascii
X-Gmane-NNTP-Posting-Host	pd9e08449.dip0.t-ipconnect.de
User-Agent	Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.4.22 (linux)
Cancel-Lock	sha1:4cwwsFu0JFyTCJv2X7UVkRBq17g=
X-BeenThere	python-list@python.org
X-Mailman-Version	2.1.15
Precedence	list
List-Id	General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe	<https://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive	<http://mail.python.org/pipermail/python-list/>
List-Post	<mailto:python-list@python.org>
List-Help	<mailto:python-list-request@python.org?subject=help>
List-Subscribe	<https://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups	comp.lang.python
Message-ID	<mailman.13642.1409380579.18130.python-list@python.org> (permalink)
Lines	18
NNTP-Posting-Host	2001:888:2000:d::a6
X-Trace	1409380579 news.xs4all.nl 2851 [2001:888:2000:d::a6]:52238
X-Complaints-To	abuse@xs4all.nl
Xref	csiph.com comp.lang.python:77316

Show key headers only | View raw

"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

Thread

Re: Keeping python code and database in sync dieter <dieter@handshake.de> - 2014-08-30 08:36 +0200

csiph-web