views:

40

answers:

1

Post your idea here. Keep it short and interesting to the general public.

When posted, your idea is up for grabs, anybody can make it happen, sell it as their own etc. etc. Who cares, as long as it gets done, right?

The background:

I came up with a great idea (but maybe it isn't or it's an utopia) and googled "rails feature request". (I'll post it later)

The rails project at lighthouse says this:

Creating a feature request: Please don't. If you want a new feature in Rails, you'll have to pull up your sleeves and get busy yourself. Or convince someone else to do it. See the contributor guide on how to get going. But posting them here is just going to lead to ticket root.

Yeah, I get this, it's OSS and there are real persons spending their own time on the project. And we love them for it! Truly, I'm awed by their efforts. But is it utterly useless or wasteful with feedback from the community about related ideas, suggestions or, well, feature requests they don't know how to implement themselves?

A: 

Version controlled migrations.

I've been having problems with migrations and a heavily changing domain. What I would like, is the possibility to run the migrations with the models it was originally designed for.

Wish: run migrations against specified versions of the code base.

self.up
  use :tag => :migrate_order

  perform_schema_actions
  update_some_data  

  use :HEAD
end

self.down
  use :tag => :a_previous_migration
  perform_schema_actions
end

Not very unobtrusive perhaps, but migrations are in nature stateful and must be run in a sequence. I guess this isn't a trivial problem, but I could use a solution, that's for sure.

Ole Morten Amundsen