The Rails 4 Way page 177: Sebastian says… A little-known fact is that you can remove old migration files (while still keeping newer ones) to keep the db/migrate folder to a manageable size. You can move the older migrations to a db/archived_migrations folder or something like that. Once you do trim the size of your … Read more
Check out response below by Paul for some notes on compatibility with newer versions of Django/South. This seemed like an interesting problem, and I’m becoming a big fan of South, so I decided to look into this a bit. I built a test project on the abstract of what you’ve described above, and have successfully … Read more
Create a model with a text field > rails g model Arches thearray:text invoke active_record create db/migrate/20111111174052_create_arches.rb create app/models/arches.rb invoke test_unit create test/unit/arches_test.rb create test/fixtures/arches.yml > rake db:migrate == CreateArches: migrating =================================================== — create_table(:arches) -> 0.0012s == CreateArches: migrated (0.0013s) ========================================== edit your model to make the field serialized to an array class Arches < … Read more
What you’re trying to do is possible, and I would say the correct thing to do. You need, though, to reload the column info for the model classes you’re updating in the migration, so that Rails knows about the new columns. Try this: def.self up add_column :users, :age_text, :string User.reset_column_information users = User.find(:all) users.each do … Read more
Actually, the version is much more important than this. The code you’ve cited is actually only a small part of what assume_migrated_upto_version does. The real effect of the migration version is that all prior migrations (as found in the db/migrate directory) are assumed to have been run. (So yes, it does what the function name … Read more
Simply specify the key name when creating it (with the second argument for primary). $table->primary([‘column_1’, ‘column_2’, ‘column_3’], ‘my_long_table_primary’); Next, If you have error like You have an error in your SQL syntax … after this modification please make sure you are not using reserved word by your database engine for your key name. Eg for … Read more
I agree with Laksham that you should avoid this situation. But sometimes, we have to. I’ve faced this situation in the past and I’ve managed it this way. If you want to avoid losing data you can dump the old application data into a json file. python manage.py dumpdata old_app –natural –indent=4 1> old_app.json Note … Read more
it has already been mentioned in this post : https://community.jboss.org/message/744530#744530 , you can just ask the resteasy module to not scan for other JAX RS implementations in your webapp; just add this to your web.xml : <context-param> <param-name>resteasy.scan</param-name> <param-value>false</param-value> </context-param> <context-param> <param-name>resteasy.scan.providers</param-name> <param-value>false</param-value> </context-param> <context-param> <param-name>resteasy.scan.resources</param-name> <param-value>false</param-value> </context-param> worked fine for me