Re: conflicting advice about has_a and primary keys

[prev] [thread] [next] [Date index for 2004/05/18]

On Tue, May 18, 2004 at 02:04:22PM -0400, Perrin Harkins wrote:
> The CDBI docs contain this piece of advice in the has_a() section:
> "*NOTE* You should not attempt to make your primary key column inflate
> using has_a() as bad things will happen. 
> A little further down in the many-to-many section, it breaks this rule.
> Which of these is correct?  Or is it just that using has_a() on your
> primary key fails if you specify an inflate() method?

To be honest I'm not sure.

The warning under has_a is there as people reported bad things
happening.

However, the MCPK linking table thing seems to work.

So, I don't know if the caveat is out of date, or if there's something
different in the linking table scenario.

Hopefully, however, if I can ever find some time in the increasingly
surreal corporate soap opera that is currently my life, and get the
changes finished off so that attributes are objects rather than simple
scalars, and can thus hold several different pieces of information
simultaneously (database value, current value, inflated value, etc.)
we can sort all of this out anyway.

Tony