Jeremy Evans wrote: > I'd suggest just adding a subclass of Sequel::SQL::Expression. Maybe > supporting an API like: > > Jeremy, After delving a little deeper into handling hstore in sequel, the changes are far from trivial, for me, anyway. It seems to me that a simpler approach might be to just have a conventional pg table with k & v columns with the row(s) linked to the parent table. This of course, would be easily handled by sequel without any changes. Do you think implementing hstore would have any worthwhile advantages over this simpler approach? Paul
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
