You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When new asynchronous child message is created then it has identical msgTimestamp as parent message. There is SQL query for garanteed order where you can find "ORDER BY m.msgTimestamp".
From this is not clear which message (parent or child) will be processed firstly - if first is parent message then child message won't be processed anymore, if first is child message then it will be ok.
Reference: CLVBUS-168
The text was updated successfully, but these errors were encountered:
When new asynchronous child message is created then it has identical msgTimestamp as parent message. There is SQL query for garanteed order where you can find "ORDER BY m.msgTimestamp".
From this is not clear which message (parent or child) will be processed firstly - if first is parent message then child message won't be processed anymore, if first is child message then it will be ok.
Reference: CLVBUS-168
The text was updated successfully, but these errors were encountered: