ronin

Leonard Lin: Internet Asshattery, Armchair Scaling Experts Edition

Looks like the Rails scaffolding doesn’t like it when your model uses a different table name from the default mapping it expects(like when accessing a legacy database model).

So if you have a model like so:

class Thing < ActiveRecord::Base
    set_table_name "some_thing"
end

Then ActiveRecord will be expecting a table called “some_thing”, however the scaffolding generator is expecting the default, which is going to be “things”(or something like that since I can’t be bothered actually generating a model called Thing).

When running your generator you’re going to end up with an error like:

error  Before updating scaffolding from new DB schema, try creating a table for your model (Thing)

Annoying as this is, you can work around it by temporarily creating the table required by the generator. Then go ahead and drop it after the generator works.

create table things ();

I’m not sure what longer term effects this causes, and if there is a better way then let me know.

Blaine Buxton’s slides on scaling twitter.

James Shell: Seaside, Rails, Helpers…

It’s not XML, YAML, An Array or list. It doesn’t get translated into any structure like that.

Gyre: simple, fast, cross-platform, web-centric, open source, and written in Ruby.

Good idea, hope it works out.