Thanks! I think that we are going to revise our code...eventually. I'm already trying to evaluate and plan for that.
Right now I'm actually having an issue not with a frozen dataset but with a frozen expression, particularly a BooleanExpression. Just firing up IRB and requiring Sequel and as soon as it is created it is frozen. This is not true in v 4.4.41 (either in Ruby 2.2.1 or 2.4.0). I don't suppose there is a way to mitigate this for now other than replacing an existing expression with a new one? -Michael On Tuesday, February 7, 2017 at 10:02:03 AM UTC+2, Jeremy Evans wrote: > > On Monday, February 6, 2017 at 11:49:29 PM UTC-8, Michael Faughn wrote: >> >> I am getting into the maintenance of a fairly complex codebase that is >> built on top of Sequel. This code apparently relies on the ability to >> mutate datasets. Moving to Ruby 2.4.0 and the latest version of Sequel has >> then not been smooth sailing. Please forgive my relative newbness but is >> there a way to restore the ability to mutate datasets? >> > > You can still mutate datasets in Sequel 4. Assuming you don't call freeze > or use the freeze_datasets extension, the datasets should not be frozen. > > In any case, Sequel 5 will drop support for unfrozen datasets, all > datasets will be frozen and there will be no supported way to have unfrozen > datasets. So you should probably fix your code so it returns modified > copies of datasets instead of mutating them, assuming you want to upgrade > to Sequel 5 when it is released. > > 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.
