Migration stuck when running schema migration + data migration in the same migration file with postgres replication

We had the folllowing problem: - We created a migration file that was adding a new field in one table - In the same migration file of the schema migration, we also added a data migration to populate this field Locally and in our sandbox the migration worked fine, without problem. It took ~30

Re: pgadmin vs schema migration

On Feb 24, 9:54 am, ggavy wrote: > Thanks. It's good to get a little second opinion. I'm sure I'll make > the switch to migration tools eventually as things become a little > more involved. > > Cheers > gav I think the only possible danger is that you might forget

Re: pgadmin vs schema migration

Thanks. It's good to get a little second opinion. I'm sure I'll make the switch to migration tools eventually as things become a little more involved. Cheers gav On Feb 24, 11:58 am, Mike Ramirez wrote: > On Thursday, February 24, 2011 03:48:18 am ggavy wrote: > > > Hello

Re: pgadmin vs schema migration

On Thursday, February 24, 2011 03:48:18 am ggavy wrote: > Hello everyone, > if I have a live app running off a postgres db (containing data) > and I want to make reasonably simple schema (and possibly data > content) changes, are there any dangers in just using pgadmin (e.g > adding a column)

Re: pgadmin vs schema migration

On Thu, 2011-02-24 at 03:48 -0800, ggavy wrote: > I'd keep my models.py up-to-date with any changes I make > to the database (in case of future uses of the app). I haven't seen > anything online warning me not to do it, but the separation worries me > slightly well, that is the way django does

pgadmin vs schema migration

Hello everyone, if I have a live app running off a postgres db (containing data) and I want to make reasonably simple schema (and possibly data content) changes, are there any dangers in just using pgadmin (e.g adding a column) as opposed to using some type of migration software, e.g. south.

Re: Manual schema migration

On Aug 2, 12:57 pm, Torsten Bronger <bron...@physik.rwth-aachen.de> wrote: > Hall chen! > > Does anybody know a tutorial for Django-related schema migration by > using the SQL console directly?  (Preferably PostgreSQL.)  We > evaluate South at the moment, but we'd like

Manual schema migration

Hallöchen! Does anybody know a tutorial for Django-related schema migration by using the SQL console directly? (Preferably PostgreSQL.) We evaluate South at the moment, but we'd like to have the low-level knowledge as a fallback. Of course, general SQL knowledge can be assumed. It needn't

Jython Compatable Schema migration

Hi to all I am using Jython 2.5.1 and Django 1.1 ..plz help which is the compatable schema migration Thanks in advance -- View this message in context: http://old.nabble.com/Jython-Compatable-Schema-migration-tp27999390p27999390.html Sent from the django-users mailing list archive

Re: schema migration

The way to go is South: http://south.aeracode.org/ Shawn On Feb 24, 2010, at 11:51 PM, vishal d wrote: > Hi to all > > Am new to django...plz suggest me which is the better one for the > schema migration for django apps > > Thanks in advance > > vishal

schema migration

Hi to all Am new to django...plz suggest me which is the better one for the schema migration for django apps Thanks in advance vishal 2009vis...@gmail.com -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this g

Re: schema migration

+1 on South Shawn On Feb 24, 2010, at 7:20 AM, Gonzalo Delgado wrote: > El 24/02/10 09:16, dj_vishal escribió: >> plz suggest me which is the better one for the schema >> migration for django apps >> > > http://south.aeracode.org/ > > -- > G

Re: schema migration

El 24/02/10 09:16, dj_vishal escribió: > plz suggest me which is the better one for the schema > migration for django apps > http://south.aeracode.org/ -- Gonzalo Delgado <gonzalo...@gmail.com> -- You received this message because you are subscribed to the Google Groups

schema migration

Hi to all Am new to django...plz suggest me which is the better one for the schema migration for django apps Thanks in advance vishal 2009vis...@gmail.com -- View this message in context: http://old.nabble.com/schema-migration-tp27714179p27714179.html Sent from the django-users

Re: Database schema migration - any tools available?

There are quite a few that take different approaches. Your best bet may be to use the search feature with the keywords 'schema migration' within the group. On Aug 28, 10:05 am, Alex <[EMAIL PROTECTED]> wrote: > Hi all, > > I have a migrations tool made by me for an internal projec

Database schema migration - any tools available?

Hi all, I have a migrations tool made by me for an internal project. I couldn't find anything at the time and I made my own. It uses the Command pattern (took the idea from the Rails migrations) and plain MySql queries with a parser made with Antlr ... I know it is not portable but this may be

Re: Django Schema Migration

Here is Schema Evolution Project home site: http://code.google.com/p/django-schemaevolution/ Any feedbacks are welcome daev wrote: > It's very funny but couple of dayes ago I start to write some schema > wvolution framework for django. I've read articles in django-code wiki > about schema

Re: Django Schema Migration

It's very funny but couple of dayes ago I start to write some schema wvolution framework for django. I've read articles in django-code wiki about schema evolution and make some major decisions. I realized that the better way(for me) not to analize application model definition but to analize

Re: Django Schema Migration

FYI, this is very similar to the approach we've used since 2001 when doing schema updates of our product, DynaCenter (http:// www.racemi.com). It has nothing to do with Django but the problem domain is the same. Our scripts are called "alter scripts" instead of migrators. We also added

Re: Django Schema Migration

On 4/20/07, Mike H <[EMAIL PROTECTED]> wrote: > It seems to be working well for the developers here, so here's hoping > it's useful for some other people too :) This is interesting-- migrating django apps using django. Are there cases where Django or the DB could become so broken that the

Re: Django Schema Migration

Hi Jeremy, I see your point, and yes, migrations can be run out of sequence - although in practice I've found that it is rarely an issue and if it is, it can be resolved fairly simply. Let's take a couple of examples. I'm not trying to be condescending, just thinking it through outloud ;) 1)

Re: Django Schema Migration

GREAT WORK! Migrations are being discussed for years and now we have some real-life solution. And I must say - it works and helps. Now we should get rid of SQL, we need some nice DSL syntax. David --~--~-~--~~~---~--~~ You received this message because you are

Re: Django Schema Migration

Hi again, The docs have been updated with the points you raised. Cheers! Mike On 4/20/2007, "Mike H" <[EMAIL PROTECTED]> wrote: > > >Ah, yes, the docs aren't clear on this at the moment, but the automatic >schema creation does not run if you use migrations for an application. >You will

Re: Django Schema Migration

Ah, yes, the docs aren't clear on this at the moment, but the automatic schema creation does not run if you use migrations for an application. You will have to create a migration that creates the tables. (Just use 'python manage.py sqlall' to get the sql for the migration) The reason for this

Re: Django Schema Migration

Thanks for an advice. I found problem with migrations when running tests - python manage.py test . It seems that migration is run before django creates table based on model. Tests should probably not run migratons at all. --~--~-~--~~~---~--~~ You received this

Re: Django Schema Migration

Ah, thanks for the heads up! Unfortunately, syncdb will install the latest SQL for all installed applications (as far as I am aware). Is there a way just to install the schema for a specific application? I guess I could call sqlall and run each supplied statement, but that's pretty much just

Re: Django Schema Migration

Hi David, The python functionality is there so that you can manipulate the models directly or run more complex dynamic sql if you need to. Let's say that your app is called "myapp" and you want to do something special to all User records with an aol email address, but that something special is

Re: Django Schema Migration

How can 'Python migrations' be used? Can someone explain or place some example? Where should I put the function? --- excerpt from docs --- Using Python migrations Sometimes it might be easier to do your migration using Python and the Django models. To define a python migration, simply define a

Re: Django Schema Migration

Actually, those ramblings might not be relevant just yet... I made a simple patch to syncdb to see if an application has a migrations module or not. If it does, it will run it. If not, it will do its automated thing. Seems to work quite well at the moment and let me get rid of about a third of

Re: Django Schema Migration

Yeah, eventually I'd like to have the migrations define column additions, deletions and renames using the models from Django. However this is my first foray into the internals of Django so I would have a lot of reading to do! I'm wondering if the schema-evolution branches would have code I can

Re: Django Schema Migration

Hey, this is neat! It's just a shame that it doesn't use Python models or some type of database agnostic representation - any plans there? Great work non the less though! -- Ollie > Hi all, > > Release 0.01 of the migration module can be downloaded from > http://www.aswmc.com/dbmigration/ >

Re: Django Schema Migration

Hi all, Release 0.01 of the migration module can be downloaded from http://www.aswmc.com/dbmigration/ as well as a patch to integrate it into the syncdb command. It seems to be working well for the developers here, so here's hoping it's useful for some other people too :) MikeH

Re: Django Schema Migration

On 4/20/07, Mike H <[EMAIL PROTECTED]> wrote: > > Before I release the code, I want to make the migrator call 'install' > from django.core.management if it doesn't find a migration module for > an app. Also, as this is being done as part of a work project, I have to > get permission to release

Re: Django Schema Migration

Thanks Ned, that's certainly something I want to bear in mind. At the moment the dbmigration code only uses sql migrations, but the way the migrator is put together will allow me to build support for migrations written in python quite easily. Before I release the code, I want to make the

Re: Django Schema Migration

Just one comment on this: At Tabblo, we've found it very useful to have not only SQL migrations, but Python migrations as well, because database migrations involve not just schema changes, but also data changes. While SQL can be used to update the data, it can be much easier to do it with

Re: Django Schema Migration

On 4/19/07, Mike H <[EMAIL PROTECTED]> wrote: > > I've been working on a tool to give me an automated way of altering the > schemas on servers I deploy my django applications to. I know about the > schema-evolution branch, but the current approach of that isn't > completely automated and the work

Re: Django Schema Migration

Hello, Can you share the initial code with us? This approach seems to be good. Do you have experience on some project? David Mike H napsal: > Hi all, > > I've been working on a tool to give me an automated way of altering the > schemas on servers I deploy my django applications to. I know about

Django Schema Migration

Hi all, I've been working on a tool to give me an automated way of altering the schemas on servers I deploy my django applications to. I know about the schema-evolution branch, but the current approach of that isn't completely automated and the work seems to have stopped on it. The approach I