Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #77279 > unrolled thread

Re: Keeping python code and database in sync

Started byJean-Michel Pichavant <jeanmichel@sequans.com>
First post2014-08-29 18:49 +0200
Last post2014-08-29 18:49 +0200
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python


Contents

  Re: Keeping python code and database in sync Jean-Michel Pichavant <jeanmichel@sequans.com> - 2014-08-29 18:49 +0200

#77279 — Re: Keeping python code and database in sync

FromJean-Michel Pichavant <jeanmichel@sequans.com>
Date2014-08-29 18:49 +0200
SubjectRe: Keeping python code and database in sync
Message-ID<mailman.13612.1409331046.18130.python-list@python.org>

----- Original Message -----
> From: "Roy Smith" <roy@panix.com>
> 
> Yeah, schema migration is an ugly problem.  There's a number of tools
> to
> help here, most of which reduce the suckitude, but don't eliminate it
> completely.  Some things you might want to look at:
> 
> * SQLAlchemy Migrate
> * South (django-specific)
> * yoyo-migrations
> * alembic
> 
> Google for "python schema migration tools" and you'll probably find
> others.

Note that South is now fully integrated in django 1.7 (It's still ugly but it has been polished by the django team).
The OP may want to consider moving to such framework, they tend to provide working concepts on critical issues when it comes to webapp/database.

JM


-- IMPORTANT NOTICE: 

The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web