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
I don't think it makes sense to always check unique & foreign key constraints within the background copy operation, since all the inserts are done against the primary key. Copied data would already be consistent in the original table.
Something like this could speed things up, I'm seeing an improvement in my use case.
I don't think it makes sense to always check unique & foreign key constraints within the background copy operation, since all the inserts are done against the primary key. Copied data would already be consistent in the original table.
Something like this could speed things up, I'm seeing an improvement in my use case.
This could be enabled with an option, or when it can be proven safe (when the migration doesn't add any new constraints). Thoughts?
The text was updated successfully, but these errors were encountered: