Re: Temporary ID hasn't been replaced on commit

From: Juergen Saar (juerge..saar.org)
Date: Thu Dec 10 2009 - 10:03:27 EST

  • Next message: Andrus Adamchik: "Re: Temporary ID hasn't been replaced on commit"

    I've seen it too, but it's not really what I'm looking for ... it
    should be good for a workaround, so that I can find my PrimaryKey

    What I'm not really sure with Cayenne-3: What is the Best Practise for
    Batchprocessing really big Resultsets. I used the ResultIterator
    because of it's small footprint.

    2009/12/10 Michael Gentry <mgentr..asslight.net>:
    > I haven't used it before, but I see a nextRow() method in
    > ResultIterator that may be what you are looking for.
    >
    > mrg
    >
    >
    > On Thu, Dec 10, 2009 at 4:21 AM, Juergen Saar <juerge..saar.org> wrote:
    >> Hi,
    >>
    >> there seems to be a change in org.apache.cayenne.access.ResultIterator
    >> with version 3 ... I'm missing the method  nextObjectId(DbEntity
    >> entity) ... in the API-Docs it is still documented.
    >>
    >> I used this method to reduce assignment of memory space while working
    >> with big results.
    >>
    >> Any advice for me?
    >> -Juergen-
    >>
    >> org.apache.cayenne.access
    >> Interface ResultIterator
    >>
    >> 2009/11/25 Andrus Adamchik <andru..bjectstyle.org>
    >>>
    >>> As you probably know, we are already in Beta and Cayenne runtime framework code is frozen. So it is 100% stable from the API perspective. And after 1 or 2 intermediate releases it becomes final. Timewise, I don't know, maybe a couple of months?
    >>>
    >>> Andrus
    >>>
    >>> On Nov 25, 2009, at 3:47 PM, Juergen Saar wrote:
    >>>
    >>>> I'm in preparations for 3.0 ... but there was a lot of trouble this year, so
    >>>> I didn't get as far as I planned ...
    >>>>
    >>>> For using 3.0 in productive environment ... Is there a time-scale for the
    >>>> final 3.0?
    >>>>
    >>>>
    >>>> 2009/11/25 Andrus Adamchik <andru..bjectstyle.org>
    >>>>
    >>>>> 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 : Thu Dec 10 2009 - 10:04:07 EST