Hi John, thanks for the input—yeah, that would have been one way. Unfortunately that would have required a bit of a major rewrite of existing functionality which is heavily based on business logic the DataObjects.
Ended up inserting the same number of empty rows as the ordered objects were, fetching them back ordered by the DB-generated PK, and populating the empty rows with the final data. I'll then deal with the resulting emotional issues in therapy. Cheers, - hugi > On 1 Nov 2018, at 14:58, John Huss <johnth...@gmail.com> wrote: > > Without having more details my general recommendation would be to handle > the details up front before you get to the Cayenne level. Put things in > order in memory and then create your Cayenne Objects and commit them one at > a time. > > On Thu, Nov 1, 2018 at 9:35 AM Hugi Thordarson <h...@karlmenn.is> wrote: > >> Hi all. >> I have a set of new (uncommitted) objects that I need to insert into the >> DB in a certain order. For… Reasons. (let's hear it for legacy DBs with >> meaningful PKs, yay!) >> >> The action is not performance sensitive and the whole thing occurs within >> a transaction, so performing multiple commits is OK. My initial though was >> that when saving, I could just iterate through the new objects, localizing >> each one in a new ObjectContext and committing that on each iteration—but I >> haven't found a way to get that to work. >> >> Any ideas? >> >> Cheers, >> - hugi
