On Tuesday, April 29, 2014 10:26:48 AM UTC-7, Snarke wrote:
>
>
> On Apr 29, 2014, at 10:02 , Jeremy Evans wrote:
>
> > You shouldn't need to do that. Just:
> >
> > DB = Sequel.connect(...)
> > DB.extension :pg_hstore
> > Sequel.extension :pg_hstore_ops
>
> Well, still, one must put the DB.extension part AFTER one defines DB,
> mustn’t one? I know, obvious once I got the error message. {chuckle}
>
A lot of things with Sequel are order dependent, and it's not always
obvious why (e.g. why should pg_hstore be loaded before pg_hstore_ops).
I've written a guide to try to explain in which order things should be
done (http://sequel.jeremyevans.net/rdoc/files/doc/code_order_rdoc.html).
> What Sequel could really use is a cookbook. “If you want to do X, you can
> get there in Sequel by doing these things.” I know I’ve leafed through such
> things before and said “Oh! Yea, I DO want to do X! I hadn’t even
> considered that as an option, but of course I want to do that.”
I think the general problem with a cookbook is that each recipe is
generally only helpful to a small percentage of people. So you might read
the whole cookbook and find a single thing that is helpful.
Don't get me wrong, Sequel should be better documented, but I prefer to
document things in a structured manner, as opposed to a cookbook with a
bunch of unrelated recipes. However, I do not want to discourage anyone
else from writing such a cookbook, if they are so inclined.
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 http://groups.google.com/group/sequel-talk.
For more options, visit https://groups.google.com/d/optout.
