On 2/22/06, Nathaniel S. H. Brown <[EMAIL PROTECTED]> wrote:
> I am pretty sure this has been brought up elsewhere, and have heard it
> discussed a few places myself.
>
> I want to know what thoughts surround the concept of having ActiveRecord
> have methods such as
>
> class Model < ActiveRecord::
I am pretty sure this has been brought up elsewhere, and have heard it
discussed a few places myself.
I want to know what thoughts surround the concept of having ActiveRecord
have methods such as
class Model < ActiveRecord::Base
column :first_name, :string => 255
column :description, :text
Fixture accessor methods don't work with set_table_name because the
class name can't be inferred from the table name. I've created a patch
which fixes this (http://dev.rubyonrails.org/ticket/3935).
Please take a look and throw suggestions my way.
Here's the current usage for a model Joke which us
Hi Kevin et al,
Thanks very much for the encouragement and advice. Just to
summarize, the best plan appears to be:
a) Create a plugin ("activedata")
http://wiki.rubyonrails.org/rails/pages/HowTosPlugins
b) Define my own module containing my custom classes ("ActiveData")
c) Define a new gen
On 2/22/06, Pete Yandell <[EMAIL PROTECTED]> wrote:
> Does this tie in with http://dev.rubyonrails.org/ticket/1562 which
> allows including multiple associations that reference a single table,
> but (AFAIK) isn't compatible with edge rails? If this doesn't solve
> the same problem as 1562, would th
Does this tie in with http://dev.rubyonrails.org/ticket/1562 which
allows including multiple associations that reference a single table,
but (AFAIK) isn't compatible with edge rails? If this doesn't solve
the same problem as 1562, would this make solving it easier?
On 22/02/2006, at 8:30 AM
