Holger Hoffstätte writes:
>> At 01:55 PM 11/17/2002 +0100, Holger Hoffstätte wrote:
>>>Another reason might be that the assumed mapping of Class to ObjEntity
>>> might not always be true or desired. How likely are scenarios like you
>>> could have with EOF's EOGenericRecord, where you really don't care
>>> about the class but just want to use a dumb record?
>
> Very likely, for eample in the unit tests which you've successfully
> broken. Good work, Holger :->
Yeah, I haven't looked into details, but the nightly build failed today
because of the unit test problems. [I should probably change the script to
send report email to cayenne-cvs]
> I could:
> - change the tests to use 'real' classes (Artist in this case)
> - de-deprecate the registerNewObject() method with the objEntityName
> - fix the deprecated method for now so it works again, and keep using the
> deprecated method in the test for now
I support the second one of the three. I would keep around support for the
entity names for a while, even if we don't emphasize it to the users.
Andrus
This archive was generated by hypermail 2.0.0 : Mon Nov 18 2002 - 10:19:16 EST