Hi all
I've spotted a quirk with the PAY_ELEMENT_ENTRY_API.UPDATE_ELEMENT_ENTRY api.
If I call it with P_VALIDATE set to TRUE the update still takes place.
I have a recreatable scenario here which is a bit alarming.

Before i wander off to Oracle with my rant i was wondering if anyone else has encountered this as well (or is it just me and the set-up here)?

Cheers

Baz

I too find the same confusion, But document says something ....hmmm

p_validate
----------

This parameter is used to control whether the database is updated or not. The default is False, which means that the API performs normally by doing all neccesary validation, insert, update or deletes.

If it is set to True then the API will just check that the operation will be valid. All insert,update or delete operations are rolled back.

Note: There are no commits done from within the API. These must be done from the calling program.

Indeed i'm aware that no commits are performed within the API, however i am questioning whether the rollback is actually occuring when P_VALIDATE is set to TRUE.
I have tested several cases here and my findings are indicating that the rollback does not occur in the UPDATE API.

COnfused?