Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

WriteNow parameter of Obj-Save method causes warning

Suggest edit Updated on September 22, 2020

 This presentation is part of the Designing and Building for Performance Self-Study Course.

 

Transcript

PRPC's default behavior for performing Obj-Save is to "defer" the actual UPDATE/INSERT SQL command until a Commit is issued.  The benefits of this deferral are the ability to perform multiple, back-to-back saves on the same object instance and PRPC will combine these updates into a single cumulative update at the time of commit thus decreasing the interval of time in which locks are held within the database.  This maximizes concurrency within the application.

Specifying "WriteNow" defeats all the benefits of the deferred save feature.

There are legitimate reasons to performing a WriteNow, such as needing to immediately re-read this instance before issuing a commit.  Use of this method can be dangerous if proper locking and error checking is not done.  This is not common practice, however, which is why these are called "Warnings" and not "Errors."

Did you find this content helpful? YesNo

50% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us