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
{{ message }}
Repository navigation
Studio doesn't show errors from duplicated key #786
This seems to be a studio / console issue(?). So, the unique index seems to work correctly but in case of a single insert no error is reported back. However, the server logs a duplicate entry error.
I reopened the issue and changed the name. You're right, the problem is with Studio, or better, with the HTTP layer. The duplicated key is thrown at commit time after the error code 200 is already sent back. What it's needed is a refactoring on that part to send the HTTP response code after the commit.
Activity
gramian commentedon Jan 23, 2023
@lvca This also does not work if I do
between
INSERTs.gramian commentedon Jan 29, 2023
This seems to be a studio / console issue(?). So, the unique index seems to work correctly but in case of a single insert no error is reported back. However, the server logs a duplicate entry error.
[-]Unique Index does not error on single non-unique insert[/-][+]Studio doesn't show errors from duplicated key[/+]lvca commentedon Jan 29, 2023
I reopened the issue and changed the name. You're right, the problem is with Studio, or better, with the HTTP layer. The duplicated key is thrown at commit time after the error code 200 is already sent back. What it's needed is a refactoring on that part to send the HTTP response code after the commit.
fix: http api, fixed duplicated exception thrown after http status co…
chore(deps): bump org.apache.maven.plugins:maven-shade-plugin from 3.…
fix: http api, fixed duplicated exception thrown after http status co…
chore(deps): bump org.apache.maven.plugins:maven-shade-plugin from 3.…