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? I'm hearing: - dump postgres (in this case postgres :) ) - create new db - restore postgres - create first migration to say add a column or something. Thanks so much, On Saturday, January 7, 2017 at 2:45:01 PM UTC-8, Jeremy Evans wrote: > > On Saturday, January 7, 2017 at 2:30:05 PM UTC-8, Fred Joe wrote: >> >> Howdy, >> >> I want to start managing a database. I've looked through FAQs and this >> group to attempt to find some sort of direction here. I may have missed >> it. If I have missed the existing FAQs I do apologize. Please kindly >> point me in the right direction. >> >> What I have: >> - an existing database with a lot of tables, FKs, etc. >> >> What I want to do: >> - manage the database versions with this module moving forward. >> >> Options I see: >> 1. Start migrating from here with Sequel so the first change from here is >> "version 1". >> 2. Dump the entire schema currently into sequel speak and attempt to fake >> that into being version "1" of the schema. Then the first "change" is >> "version 2". >> >> I realize can go either of these routes and maybe some other possible >> methods but I wanted to make sure i was inline with the intent of the >> author. I'm sure there's a preferred method. Before I break stuff in my >> database I wanted to reach out. The issue being we didn't start from >> scratch with Sequel. I assume starting with Sequel is the more normal >> case. I'm always concerned about living on the "edge" (case). :) >> >> Any advise would be much appreciated, >> >> Thanks so much, >> > > In this case, you should probably do a database schema dump for the > current database (using the database's tools). Then before using Sequel in > a new database, load this schema dump into the database (using the > database's tools). After that, you can use Sequel's migration to manage > database changes. This is basically option 1. > > Option 2 is possible, but probably a lot more work if you are doing > anything advanced in the database (functions, triggers, constraints). > > 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.
