I'm a huge fan of Sequel, and we use it extensively throughout our database service. It makes a great compromise between traditional Rails developers who prefer to keep their noses clean and stay out of SQL and database-centric engineers who know how to get in and write a custom query that will make the optimizer sing. Personally, my favorite element of SQL is the malleable Dataset, which allows me to take a query back and forth between SQL and Ruby with ease.
-p On Mon, Aug 22, 2011 at 5:26 PM, Jeremy Evans <[email protected]>wrote: > During my PgWest presentation next month, I'm planning on having a > slide about production uses of Sequel. If you are using Sequel in > production and would like to be mentioned, please reply (either > publicly here or privately to me) and let me know what you are using > Sequel for. If you want to include a company logo, that would be > helpful too. > > Also, if anyone wants to write a testimonial for using Sequel (e.g. > "We started using Sequel at XXX and found that we write code faster, > it runs faster, and it has fewer bugs"), I'd be interested in that as > well. Not just for the presentation, but possibly also for a page on > Sequel's website. > > Thanks, > 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. > > -- Peter van Hardenberg San Francisco, California "Everything was beautiful, and nothing hurt." -- Kurt Vonnegut -- 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.
