Do you have an option of trying this with 3.0? There were a few bug
fixes related to unstable data types in ObjectIds (e.g. the same ID
can have a PK mapping as a BigDecimal or Integer depending on how
object was obtained). Could be something related.
Andrus
On Nov 25, 2009, at 10:32 AM, Juergen Saar wrote:
> I'm using Version 2.0.4 ...
>
> 2009/11/25 Andrus Adamchik <andru..bjectstyle.org>
>
>> Don't yet know what might be causing it, but what version of
>> Cayenne are
>> you using?
>>
>> Andrus
>>
>>
>> On Nov 25, 2009, at 9:49 AM, Juergen Saar wrote:
>>
>> Hi,
>>>
>>> we're using cayenne for the web-interface of a 20 year old project
>>> with
>>> meaningful keys. We don't use tapestry. The keys are handled in the
>>> validateForSave().
>>>
>>> In some cases after commit there is an Exception: "Temporary ID
>>> hasn't
>>> been
>>> replaced on commit"
>>> The values of the Dataobject are OK and the Informations put to
>>> database
>>> are
>>> correct.
>>>
>>> In the Objects that cause this Exception I can't see any
>>> difference to
>>> Objects that don't cause this Execption.
>>>
>>> Is there anything I can do to force the replacement if the Temp ID
>>> or to
>>> prevent this Exception?
>>>
>>> Caching in cayenne is disabled, because there are many other
>>> applications
>>> also manipulating data in database.
>>>
>>>
>>> Any hint would help ...
>>> -Juergen-
>>>
>>
>>
This archive was generated by hypermail 2.0.0 : Wed Nov 25 2009 - 08:28:21 EST