database-migration

When I change help_text or verbose_name for any of my model fields and run python manage.py makemigrations , it detects these changes and creates a new migration, say, 0002_xxxx.py . I am using PostgreSQL and I think these changes are irrelevant to my database (I wonder if a DBMS for which these changes are relevant exists at all). Why does Django generate migrations for such changes? Is there an option to ignore them? Can I apply the changes from 0002_xxxx.py to the previous migration ( 0001_initial.py ) manually and safely delete 0002_xxxx.py ? Is there a way to update previous migration

when doing heroku run rake db:migrate all migrations are performed and then, at the end I always get following message: /app/vendor/bundle/ruby/1.9.1/bin/rake: No such file or directory - pg_dump -i -s -x -O -f /app/db/structure.sql dan79p98fykovu I can't add pg_dump to PATH on Heroku. How to deal with this? The issue is that rails is trying to dump a new structure.sql once the migration is complete, and failing because pg_dump is not present. It's pointless to generate a new structure.sql for a deployed app, so the best solution is to tell rails not to. Edit your Rakefile and override the

I want to push my local postgresql database to heroku, using heroku pg:push command. The command looks like this: heroku pg:push mylocaldb DATABASE --app sushi according to the heroku document: https://devcenter.heroku.com/articles/heroku-postgresql . Here is my local database info: Name: mysitedb User: bill Password: bill The DATABASE_URL environment variable in my machine is set to: postgres://bill:bill@localhost/mysitedb . My app's name is secure-gorge-4090 . I tried heroku pg:push mysitedb DATABASE --app secure-gorge-4090 . The output was: ! Remote database is not empty. ! Please create a

Table 'users': |id|name|address|post_code|deleted_at|created_at| and I want add column 'phone_nr' somewhere between 'id' and 'deleted_at' Is it possible by migrations in Laravel 4.1? James Binford Yes. Create a new migration using php artisan migrate:make update_users_table . Then use the table command as follows (if you're using MySQL!): Schema::table('users', function($table) { $table->string('phone_nr')->after('id'); }); Once you've finished your migration, save it and run it using php artisan migrate and your table will be updated. Documentation: https://laravel.com/docs/4.2/migrations

I've created a table using migration like this: public function up() { Schema::create('despatch_discrepancies', function($table) { $table->increments('id')->unsigned(); $table->integer('pick_id')->unsigned(); $table->foreign('pick_id')->references('id')->on('picks'); $table->integer('pick_detail_id')->unsigned(); $table->foreign('pick_detail_id')->references('id')->on('pick_details'); $table->integer('original_qty')->unsigned(); $table->integer('shipped_qty')->unsigned(); }); } public function down() { Schema::drop('despatch_discrepancies'); } I need to change this table and drop the foreign

I have a problem with pushing my migrations to the production database. The issue: I've altered database schema by adding 1 column. I've migrated it to the production database: MacBook-Air-Mac:app msc$ rake db:migrate RAILS_ENV="production" [RailsAdmin] RailsAdmin initialization disabled by default. Pass SKIP_RAILS_ADMIN_INITIALIZER=false if you need it. == AddLengthColumnToBooks: migrating ========================================= -- add_column(:books, :length, :integer) -> 0.0017s == AddLengthColumnToBooks: migrated (0.0019s) ================================ Thinking that the new DB schema