On Monday, October 1, 2018 at 11:21:43 AM UTC-7, Chris Hanks wrote: > > Hmm, seems like careless use of `constant_sql_override` could change the > output/effect of old migrations? For example, if a migration sets a column > default of CURRENT_TIMESTAMP, and then later the constant sql is set to > "CURRENT_TIMESTAMP AT TIME ZONE 'UTC'", then development/production > databases could have columns with differing default values? > > Thing to be aware of, I suppose. >
Correct, but this isn't a unique situation, the same is true of multiple other extensions (e.g. pg_timestamptz, integer64). Anytime you change Sequel::Database configuration for an application under development, you should consider whether it will affect your migrations, and plan accordingly if so. 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.
