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 using COPY INTO ... LOCKED on a non-empty table, the server reports a count which is one too high for the number of inserted values. The actual number inserted is correct, only the reporting is off.
Date: 2014-02-20 11:15:42 +0100
From: @sjoerdmullender
To: SQL devs <>
Version: 11.17.9 (Jan2014)
CC: @njnes
Last updated: 2014-03-11 09:19:38 +0100
Comment 19592
Date: 2014-02-20 11:15:42 +0100
From: @sjoerdmullender
When using COPY INTO ... LOCKED on a non-empty table, the server reports a count which is one too high for the number of inserted values. The actual number inserted is correct, only the reporting is off.
Comment 19627
Date: 2014-02-21 09:51:08 +0100
From: @njnes
We now return the correct slice (ie with the correct row count)
Comment 19697
Date: 2014-03-11 09:19:38 +0100
From: @sjoerdmullender
Jan2014-SP1 has been released.
The text was updated successfully, but these errors were encountered: