Auto-migrations and Sequel (was: Where is the rdoc for set_schema?)

2009-10-16 Thread Nate Wiger
Since we're on topic, I was actually going to post a question about auto-migrations. Basically, I'm going to have to implement auto- migrations functionality that works with Sequel anyways, since we rely heavily on it at my work. (Right now we're using AR with auto_migrations). A large part of

sequel and memcached

2009-10-16 Thread Florent
I saw that sequel has a caching feature but it's using memcache- client. I prefer the memcached version (http://github.com/fauna/memcached) that is know to be a lot faster. Problem is that memcached API is a bit different of memcache-client API. Can I create a new plugin based on caching.rb that

Re: Auto-migrations and Sequel (was: Where is the rdoc for set_schema?)

2009-10-16 Thread Jeremy Evans
On Oct 16, 8:55 am, Nate Wiger nwi...@gmail.com wrote: Since we're on topic, I was actually going to post a question about auto-migrations. Basically, I'm going to have to implement auto- migrations functionality that works with Sequel anyways, since we rely heavily on it at my work.  (Right

Re: sequel and memcached

2009-10-16 Thread Jeremy Evans
On Oct 16, 10:07 am, Florent f.monbill...@gmail.com wrote: I saw that sequel has a caching feature but it's using memcache- client. I prefer the memcached version (http://github.com/fauna/memcached) that is know to be a lot faster. Problem is that memcached API is a bit different of

Re: Auto-migrations and Sequel (was: Where is the rdoc for set_schema?)

2009-10-16 Thread Nate Wiger
I'm against auto migrations as there really isn't a way to do things properly. Let's say you have this schema: CREATE TABLE items ( id INTEGER PRIMARY KEY, number_of_items INTEGER ); And you want to migrate it to this schema: CREATE TABLE items ( id INTEGER PRIMARY KEY,

Re: Auto-migrations and Sequel (was: Where is the rdoc for set_schema?)

2009-10-16 Thread Jeremy Evans
On Oct 16, 12:51 pm, Nate Wiger nwi...@gmail.com wrote: I'm fine with an external extension, makes sense. But just some food for thought: Automatically, stuff like the above is problematic, but that's easily solved with:    column :num_items, Integer, :was = :number_of_items So if :was,

yield columns as array

2009-10-16 Thread Joel VanderWerf
Is it possible to bypass the hash creation when iterating over a dataset, and instead yield an array of specified columns to the block, like this? DB[:table].each(:column1, :column2) do |col1, col2| ... end ISTR seeing something like this somewhere, but can't find it in the rdoc now. --

Re: yield columns as array

2009-10-16 Thread Jeremy Evans
On Oct 16, 4:34 pm, Joel VanderWerf vj...@path.berkeley.edu wrote: Is it possible to bypass the hash creation when iterating over a dataset, and instead yield an array of specified columns to the block, like this? DB[:table].each(:column1, :column2) do |col1, col2| ... end ISTR seeing