On Friday, June 23, 2017 at 7:33:56 PM UTC-4, Jeremy Evans wrote: > > In order to troubleshoot this, you need to prepare a minimal, self > contained example migration file that shows the issue. >
That makes sense, I’ll get right on that — thank you! > In general, the error you are seeing should only happen if you are > rescuing an earlier exception that caused the transaction to abort. > Hmm, in my case I’m using the sequel CLI command to run a single migration file that is, I think, quite simple. I’m pretty sure I haven’t added any rescue blocks. But I’ll double-check when I prepare that example migration file that reproduces the issue. Thanks! Avi -- 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.
