On Monday, January 9, 2017 at 3:34:48 PM UTC-8, Fred Joe wrote: > > Jeremy, > > Thanks so much for the quick reply. > > The way I read this you want me to dump and restore the database prior to > using sequel to being any further changes? Can I trouble you for the why > here? >
My recommendation for dump and restore applies for bringing up a new database. In general it's a good idea to have separate databases for development/production/testing, and it's pretty common for each developer to have a separate development database. But if you are in a situation where there is only one master database, and you just want to start using Sequel migrations to make changes to it, you don't need to do anything, you can use migrations without a dump and restore. I would still highly recommend creating a schema dump before adding a Sequel migration, even if you are only using a single master database and don't need to restore it, as it will make things easier for you if you later decide to bring up another copy of the database. Thanks, Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
