Migration strategies for table dumps?

Hi,

I’m curious how folks handle situations where you want to backup
existing data in a table before performing migrations. Say, for
example, you have a column type change, and you want to preserve the
current data and later releoad that data in case something goes wrong.

Do folks manually do a Model.find(:all) and dump it to a file in, say,
yaml format in the self.up method before any schema changes occur and
then reload it in the self.down method? Perhaps as a pseudo-fixture?
Or do people use temporary tables?

What’s the preferred strategy? And are there any builtin helpers for
this? Or is it ‘roll your own’?

Regards,

Dan

This communication is the property of Qwest and may contain confidential
or
privileged information. Unauthorized use of this communication is
strictly
prohibited and may be unlawful. If you have received this communication
in error, please immediately notify the sender by reply e-mail and
destroy
all copies of the communication and any attachments.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs