Re: No overload magic

[prev] [thread] [next] [Date index for 2005/02/17]

On 16 Feb 2005, at 11:25, Michael G Schwern wrote:

> On Wed, Feb 16, 2005 at 10:05:41AM +0000, William Ross wrote:
>> In the message you cite the author was trying to perform comparisons 
>> on
>> cdbi objects and assuming that ($x > $y) is the same as ($x->id >
>> $y->id). There's no reason why that assumption should be correct: not
>> all classes have a single key, and it's just as likely that you would
>> want to compare some other column or a computed value, so cdbi leaves
>> you to specify your own overloading.
>
> I think that's a bit silly. [1]  Its not as likely you want to compare 
> some
> other column, you probably want to compare the primary keys especially
> when its an equality test.  CDBI can do the right thing by default for
> $x == $y even in the case of multiple primary keys.  Its an expectation
> that was added and now appears to have been removed?

As far as I know == still works this way. The original poster was 
expecting > to be the same, which at the moment it isn't.

It's interesting to note that the overloading of == also means that

	Class::A->retrieve($id) == Class::B->retrieve($id)

will be true, provided they exist. Is this good, bad or irrelevant?

will