[Glass] New objects

[Otto Behrens]

Thanks a lot Richard.

Otto Behrens

+27 82 809 2375
[image: FINWorks]
[image: FINWorks] <http://za.linkedin.com/in/waltherbehrens>
www.finworks.biz

Disclaimer & Confidentiality Note: This email is intended solely for the
use of the individual or entity named above as it may contain information
that is confidential and privileged. If you are not the intended recipient,
be advised that any dissemination, distribution or copying of this email is
strictly prohibited. FINWorks cannot be held liable by any person other
than the addressee in respect of any opinions, conclusions, advice or other
information contained in this email.


On Wed, Nov 12, 2025 at 8:03 PM Richard Sargent <
richard.sargent at gemtalksystems.com> wrote:

> The following method should do the trick. The comment explains.
>
> objectsToBeCommitted
> "The enumerateDirtyList: is the correct way to identify objects to be
> written in the next commit.
> List Id -1 contains the currently active dirty list.
> In a nested transaction, it includes the temporary objects reachable from
> the modified persistent
> objects.
> In a doubly nested transaction, it will include all that plus all
> temporary objects reachable from them,
> the objects which are created as part of the work in the current
> transaction."
>
> | objectsToBeCommitted |
>
>   System beginNestedTransaction.
> objectsToBeCommitted := System enumerateDirtyList: -1.
>   System commitTransaction.
> ^objectsToBeCommitted
>
> On Wed, Nov 12, 2025 at 3:38 AM Otto Behrens via Glass <
> glass at lists.gemtalksystems.com> wrote:
>
>> Hi,
>>
>> Is there a way to determine which new objects are created in a gemstone
>> session before we commit? We can use System enumerateDirtyList: to
>> determine which already committed objects are dirty, but we would like to
>> find new objects as well.
>>
>> Kind regards
>>
>> Otto Behrens
>>
>> +27 82 809 2375
>> [image: FINWorks]
>> [image: FINWorks] <http://za.linkedin.com/in/waltherbehrens>
>> www.finworks.biz
>>
>> Disclaimer & Confidentiality Note: This email is intended solely for the
>> use of the individual or entity named above as it may contain information
>> that is confidential and privileged. If you are not the intended recipient,
>> be advised that any dissemination, distribution or copying of this email is
>> strictly prohibited. FINWorks cannot be held liable by any person other
>> than the addressee in respect of any opinions, conclusions, advice or other
>> information contained in this email.
>> _______________________________________________
>> Glass mailing list
>> Glass at lists.gemtalksystems.com
>> https://lists.gemtalksystems.com/mailman/listinfo/glass
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/archives/glass/attachments/20251113/8112372f/attachment.htm>