On Wednesday, January 2, 2013 9:46:53 AM UTC-8, Michael Lang wrote: > > +1 on adding this. > > I've built web apps now with Sequel now and like to build reporting > systems in for the delivered solution whereby I often build a core > dataset in base reporting classes, then extend the dataset with > additional joins and groupings, etc. in descendent classes. This one > particularly would allow me to streamline the "builder" code chain and > probably should've thought to monkey patch like this myself. > having_more would be another one I'd like to have. > > Is there perhaps a way to add these additional features in > extension/plugins and we can optionally load? I have to imagine > Sequel's core has become pretty feature complete and most new > additions and requests are starting to be like this one and are > syntactic sugars >
It's certainly possible to add such methods via extensions, which would allay my concerns about memory use. However, one extension per method seems rather extreme. If someone can come up with additional methods they would want to add to the extension, and a good name for the extension, I'll certainly consider it for inclusion. Note that having_more doesn't make sense, since Dataset#having already acts like Dataset#where (it appends to the existing HAVING filter, it doesn't override it). Thanks, Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To view this discussion on the web visit https://groups.google.com/d/msg/sequel-talk/-/vM5kaA1kJt4J. 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.
