Radar: Anyway, I figure you have more insight into Spree DB schema etc than me, and definitely more experience, so; about "that thing" from earlier, the shit site that was my first Rails (and Spree) project. I've installed latest Spree and I'm now considering DB migration approaches to get data from the old 0.11 site to the new site:
-
Could run migrations on the new clean setup and go from there (i.e. transfer old content to the new site when the schema is in place.) However, I'm not sure how many, or which, tables I'll need to transfer the data from so it could be troublesome. I remember doing this in old PHP projects years ago, and it wasn't fun.
-
Could also import an SQL dump to the new DB and just attempt to get that running. However, I'm not sure just how much the following recent migrations in Spree could complicate things, seeing as the site is relatively old.
I looked at the Spree migrations added to your repo the past year and while they aren't many, there are some. Namely:
- 20110111122537_add_position_to_option_types.rb
- 20110314192118_remove_trailing_slashes_in_taxon_permalinks.rb
- 20110329141434_create_activators.rb
- 20110418151136_eligible_for_adjustments.rb
- 20111007143030_namespace_top_level_models.rb
- 20111107143030_migrate_namespaced_polymorphic_models.rb
- 20111128153359_new_preferences.rb
- 20111201024007_make_adjustments_polymorphic.rb
- 20111215032408_add_company_to_addresses.rb
- 20111216154844_add_inc_tax_to_tax_rates.rb
- 20111219203242_rename_inc_price_attribute.rb
With this in mind, do you have any pointers on what approach to take? Perhaps you'd do it entirely differently? It feels like I'm choosing between two bad options, but to be the best option seems to be to just import a DB dump and then run the migrations.