Nate,
I'm curious if you ever ended up writing an auto-migrations extension
for sequel?
Aman
On Fri, Oct 16, 2009 at 2:47 PM, Jeremy Evans jeremyeva...@gmail.com wrote:
On Oct 16, 12:51 pm, Nate Wiger nwi...@gmail.com wrote:
I'm fine with an external extension, makes sense.
But just some
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
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
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,
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,