Strange Error on item update

[DarioCrivelli]

I'm not sure how the log should be interpreted.
There is one event for the user+hash item, but it is just before the table restart, as evidenced by a subscription request followed by a deletion request for a different table (identified through the LS_window parameter).
I suppose that the user+hash event is actually the trigger for the restart.

Anyway, you are not bound in any way to using the same NonVisualTable object to request all your items together.
By using different NonVisualTable instances, you can subscribe to each item in the proper way.

[mnenchev]

The problem is that i wrote client api that relays only on on NVT.
My log example was not accurate.

[DarioCrivelli]

Ok. I don't understand if any issue is still in place.

Although it is not related with the latest issues, just in case,
I remind you that if you subscribe to an item in MERGE mode
and the Data Adapter only sends "delta updates" for the item
(i.e. it only includes the changed fields in the update events),
if you then switch to RAW mode, the "delta updates" will no longer be managed
and any field not included in an update event will be supplied with a null value to the client.