On Wednesday, January 17, 2018 at 9:01:45 PM UTC-8, Barbara Carradini wrote: > > I have a large, existing code base for a project that's been on hiatus. > Last time I was working on the project, all automated unit tests were > running perfectly. Now that I've come back to it, I'm suddenly hitting > errors on previously existing dataset declarations that rely on > the <table_name>__<column_name> syntax to specify a column in a particular > table (to keep things straight when joining tables that share column names). >
As mentioned in the Sequel 5.0.0 release notes, symbol splitting is now disabled by default (it was deprecated starting in 4.46.0). You can use Sequel.split_symbols = true to get the historical behavior, but it is recommended you switch to Sequel[:table][:column], or use one of the shortcut extensions like symbol_aref. The sequel-unsplit tool can make it easier to automatically convert most uses of :table__column. Whenever upgrading Sequel versions, it is recommended you review all release notes between the version you are upgrading from and the version you are upgrading to, and this is especially true any time the major version changes. 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.
