On Jun 1, 11:01 am, Jeremy Evans <[email protected]> wrote: > Looking at this post on StackOverflow (http://stackoverflow.com/ > questions/6195168/running-computation-using-multiple-sub-selects-in- > sequel), I realize that we don't allow most Expression methods on > Dataset. We do implement #as for aliasing, but that's actually a > custom method instead of including AliasMethods. Any objections to > including the following modules in Sequel::Dataset?: > > AliasMethods (removing the custom #as method) > BooleanMethods > CastMethods > ComplexExpressionMethods > InequalityMethods > NumericMethods > OrderMethods > StringMethods > SubscriptMethods
There hasn't been much response to this proposal, but the response has been generally positive (4 in favor, 1 against), so this will probably be committed soon. Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en.
