On Tuesday, February 7, 2017 at 1:11:16 AM UTC-8, Michael Faughn wrote: > > 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? >
There wasn't a public API to modify Expression objects before, so the code was already doing something it probably should not have been doing. You will probably want to change it from mutating an existing object to returning a new object. 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.
