On Wednesday, November 19, 2014 1:46:09 AM UTC-8, Chris Fitzpatrick wrote: > > I support and application that is used by a number of organizations using > Sequel. One problem that comes up from time to time is that during version > updates of the application, the migration script will sometimes, increment > the schema information migration counter, but the some of the migrations > will not have completed ( meaning there will be tables / columns missing ). >
I can't think of what would cause this, unless you were swallowing exceptions or something inside your migrations. > I've been trying to track down the cause, but our users are on a variety > of platforms, so it's been a little difficult. All are using MySQL, > however. > > What I'm curious about is if anyone knows of a way I can run a schema > check, either after a migration or periodically after a set of migrations > have been run? > Ideas/suggestions would be really helpful. > There's not a generic way to run a "schema check". Sequel provides methods such as DB.table_exists?(:table) or DB.schema(:table) that provide information on the current state of the database, so it should be possible to write whatever checks you need manually. 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 http://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
