data-migration

I've got a rails application where users have to log in. Therefore in order for the application to be usable, there must be one initial user in the system for the first person to log in with (they can then create subsequent users). Up to now I've used a migration to add a special user to the database. After asking this question , it seems that I should be using db:schema:load, rather than running the migrations, to set up fresh databases on new development machines. Unfortunately, this doesn't seem to include the migrations which insert data, only those which set up tables, keys etc. My

I have to migrate a large amount of existing data in a Postgres DB after a schema change. In the old schema a country attribute would be stored in the users table. Now the country attribute has been moved into a separate address table: users: country # OLD address_id # NEW [1:1 relation] addresses: id country The schema is actually more complex and the address contains more than just the country. Thus, every user needs to have his own address (1:1 relation). When migrating the data, I'm having problems setting the foreign keys in the users table after inserting the addresses: INSERT INTO

I quite like Rails' database migration management system. It is not 100% perfect, but it does the trick. Django does not ship with such a database migration system (yet?) but there are a number of open source projects to do just that, such as django-evolution and south for example. So I am wondering, what database migration management solution for django do you prefer? (one option per answer please) I've been using South , but Migratory looks promising as well. Migratory looks nice and simple. We use Django at work, and we've been using dmigrations . While it has its quirks, it's been useful

What's the best practice (or tool) for updating/migrating Mongoose schemas as the application evolves? Update: Tested, this does not work in its current form, its got the right idea going, I got a single migration to work with considerable tweaking of the module itself. But I don't see it working as intended without some major changes and keeping track of the different schemas somehow. Sounds like you want mongoose-data-migrations It is intended to migrate old schema versions of your documents as you use them, which is seems to be the best way to handle migrations in mongodb. You don't really

I have an application which is in BETA mode. The model of this app has some classes with an explicit primary_key. As a consequence Django use the fields and doesn't create an id automatically. class Something(models.Model): name = models.CharField(max_length=64, primary_key=True) I think that it was a bad idea (see unicode error when saving an object in django admin ) and I would like to move back and have an id for every class of my model. class Something(models.Model): name = models.CharField(max_length=64, db_index=True) I've made the changes to my model (replace every primary_key=True by

I am currently using Jenkins on my development PC. I installed it on my development PC, because I had limited knowledge on this tool; so I tested on it in my development PC. Now, I feel comfortable with Jenkins as my long term "partner" in the build process and would like to "move" this Jenkins to a dedicated server. Before this I have done few builds and have the artifacts archived from each build. In particular, the build number is very important to me for version control. How can I export all the Jenkins information from my current PC to my new server? Cédric Julien Following the Jenkins