Thank you very much for the prompt response. I was originally using ActiveRecord to do these kinds of things and while AR is relatively straightforward, I've been using it to handle a large number of tables with identical schemata and the only way I've been able to muscle it into doing what I needed to do was to use metaprogramming to create subclasses of ActiveRecord::Base on demand for each such table. This is a potentially serious memory leak since my application has thousands of these tables, and to make AR even less attractive I've been replicating these tables across several servers under a custom system for sharding. All of these issues have been addressed by use of Sequel in place of it.
-- 普通じゃないのが当然なら答える私は何ができる？ 普通でも普通じゃなくて感じるまま感じることだけをするよ！ http://stormwyrm.blogspot.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
