guess the main reason is not having ObjectID at hand after publishing an object to the database. as 308 function now returns ObjectID you should be able to solve this.
dont expect such issues here, as i dont read back all objects from the database but the object just published. so there is just one record returned from the database here!
no need to stream all in again using 999. simply save ObjectID as returned by 308 to the objects variable space as ObjectID. as soon as this variable is available its used instead of ObjectUID in all functions i have found! as you said, you can use ObjectID for all your modifications done (delete, update, ...) to objects in the database.
btw. forgot to mention, there is a slight delay in this function. so don't call it in a timecritial script. i added a 1 sec delay between writing the object to the database and reading back ObjectID, as the database seems to need some time before the id is available. might be possible to reduce this timeout, but did not do further testing as this is no issue to me. but it should be possible to reduce this wait time.
dont expect such issues here, as i dont read back all objects from the database but the object just published. so there is just one record returned from the database here!
no need to stream all in again using 999. simply save ObjectID as returned by 308 to the objects variable space as ObjectID. as soon as this variable is available its used instead of ObjectUID in all functions i have found! as you said, you can use ObjectID for all your modifications done (delete, update, ...) to objects in the database.
btw. forgot to mention, there is a slight delay in this function. so don't call it in a timecritial script. i added a 1 sec delay between writing the object to the database and reading back ObjectID, as the database seems to need some time before the id is available. might be possible to reduce this timeout, but did not do further testing as this is no issue to me. but it should be possible to reduce this wait time.
