Re: Keeping python code and database in sync

Newsgroups	comp.lang.python
Date	2014-08-29 05:55 -0700
References	<mailman.13604.1409316126.18130.python-list@python.org>
Message-ID	<1cdf6e52-e09b-40f1-8db1-db6cbbee9512@googlegroups.com> (permalink)
Subject	Re: Keeping python code and database in sync
From	Rustom Mody <rustompmody@gmail.com>

Show all headers | View raw

On Friday, August 29, 2014 6:12:06 PM UTC+5:30, Frank Millman wrote:
> Hi all

> Now that I have bitten the bullet and published my repository, I am forced 
> to change my working practices (which is a good thing!).

> The project is inherently database-driven. The python code expects to find 
> certain tables and columns in the database. As I develop new features, I 
> sometimes need to modify the database structure. In the bad old days (like 
> yesterday) I would just make the modifications and carry on. Now I have to 
> be aware that others may have downloaded the project, so I have to consider 
> how to ensure that their database is kept up to date.


There are tools like this
http://alembic.readthedocs.org/en/latest/

It may help to read that to avoid reinvention



> 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 dont think alembic can solve that.
Still it may help to study it

Thread

Keeping python code and database in sync "Frank Millman" <frank@chagford.com> - 2014-08-29 14:42 +0200
  Re: Keeping python code and database in sync Rustom Mody <rustompmody@gmail.com> - 2014-08-29 05:55 -0700
    Re: Keeping python code and database in sync "Frank Millman" <frank@chagford.com> - 2014-08-29 15:19 +0200
  Re: Keeping python code and database in sync Roy Smith <roy@panix.com> - 2014-08-29 10:54 -0400
    Re: Keeping python code and database in sync Skip Montanaro <skip@pobox.com> - 2014-08-29 12:04 -0500
    suckitude classifications [was Re: Keeping python code and database in sync] Ethan Furman <ethan@stoneleaf.us> - 2014-08-29 12:02 -0700
    Re: Keeping python code and database in sync Ben Finney <ben+python@benfinney.id.au> - 2014-08-30 06:34 +1000
    Re: Keeping python code and database in sync Chris Angelico <rosuav@gmail.com> - 2014-08-30 08:31 +1000
    Re: suckitude classifications [was Re: Keeping python code and database in sync] Chris Angelico <rosuav@gmail.com> - 2014-08-30 08:38 +1000
      Re: suckitude classifications [was Re: Keeping python code and database in sync] Roy Smith <roy@panix.com> - 2014-08-29 19:19 -0400
        Re: suckitude classifications [was Re: Keeping python code and database in sync] Chris Angelico <rosuav@gmail.com> - 2014-08-30 09:38 +1000
    Re: Keeping python code and database in sync Skip Montanaro <skip.montanaro@gmail.com> - 2014-08-29 18:47 -0500
    Re: Keeping python code and database in sync Ethan Furman <ethan@stoneleaf.us> - 2014-08-29 16:54 -0700
    Re: Keeping python code and database in sync Skip Montanaro <skip@pobox.com> - 2014-08-29 21:14 -0500
    Re: Keeping python code and database in sync Chris Angelico <rosuav@gmail.com> - 2014-08-30 12:28 +1000
    Re: suckitude classifications {taken to absurdity} Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-08-30 11:13 -0400

csiph-web