Hi,
I''m looking for a gem to copy data between the production and the
developing environment, the main reason is to offer "the real data" to
the final users (I know ideally we should have pre-production), the
process should be something like:
1. Select the environment origin and destiny from database.yml
2. Select table to copy. Ex: "user%,products%,companyies"
3. Select "all" or "updated from"... so that I
don''t have to copy
all the table
4. Select overwrite or keep for date in destiny with update from
higher than selected.
5. Select force or "rake db:rollback" to the production
environment
6. Copy with active record so that it works between different
databases.
7. In case of "rake db:rollback" auto "rake db:migrate"
I was thinking to make the gem by myself, but I was wondering that
probably somebody did something similar. Does anybody know?
Greetings
--
Miquel Cubel Escarré
+34 699 73 22 46
mcubel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
"Computers are good at following instructions, but not at reading your
mind." Donald Knuth.
"Los ordenadores son buenos siguiendo instrucciones, pero no leyendo tu
mente." Donald Knuth.
--
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.
> I''m looking for a gem to copy data between the production and the developing environment, the main reason is to offer "the real data" to the final users (I know ideally we should have pre-production), the process should be something like: > 1. Select the environment origin and destiny from database.yml > 2. Select table to copy. Ex: "user%,products%,companyies" > 3. Select "all" or "updated from"... so that I don''t have to copy all the table > 4. Select overwrite or keep for date in destiny with update from higher than selected. > 5. Select force or "rake db:rollback" to the production environment > 6. Copy with active record so that it works between different databases. > 7. In case of "rake db:rollback" auto "rake db:migrate" > > I was thinking to make the gem by myself, but I was wondering that probably somebody did something similar. Does anybody know?Dont'' think it will do all of what you want, but look into https://github.com/ricardochimal/taps 3/4 are going to be the problematic ones as they tend to be more "business related"... Also, what about... 3a. Handle data that''s been deleted... -philip -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.