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
I just pushed a commit that includes all of these except SubscriptMethods in Sequel::Dataset. .sql_subscript on a Dataset raises an error on PostgreSQL because that syntax is not supported. Odds are that nobody is using a dataset which returns a single array as a scalar from which they want to extract a particular entry, anyway. 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.
