Postgres complex insert or update with 2 unique constraints
I have a table that has these key columns. Other columns are present but these are the key columns for this question.
user_id: string,
external_id: string
disabled_by: string
Additional notes:
- All columns have the not null constraint.
- unique constraint ('external_id_constraint_1') (external_id, disabled_by)
- unique constraint ('external_id_constraint_2') (user_id, external_id)
Operations:
Add external id
Adding an new external id for user 1 it would look like this:
insert into external_ids (user_id, external_id, disabled_by) values ('user1', 'exid2', '');
Disabling an external id
If the external id is later revoked for user 1:
update external_ids set disabled_by='admin1' where user_id='user1' and external_id='exid2';
Reenabling the external_id
A user can't have more than 1 entry for a given external_id. If a row exists ('user1', 'exid2', 'admin1') then the row needs to be updated:
update external_ids set disabled_by='' where user_id='user1' and external_id='exid2';
Rather than a new row being created. However another user between the disable and the reenable attempt could have claimed the external_id. If this has happened the update should do nothing.
Solutions attempted
I am trying to get a single postgres sql statement to handle this case.
Things I tried:
- an insert into .... on conflict on constraint ... except that I need to handle 2 different constraint violations differently.
- update does not have the ability to do the insert if there is nothing to update
- update doesn't have the ability to handle a constraint violation.
Question:
Is it possible to do this in a single sql statement or am I doomed to be frustrated.
postgresql
asked 5 mins ago
PatPat
1011
New contributor
Pat is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I have a table that has these key columns. Other columns are present but these are the key columns for this question.
user_id: string,
external_id: string
disabled_by: string
Additional notes:
- All columns have the not null constraint.
- unique constraint ('external_id_constraint_1') (external_id, disabled_by)
- unique constraint ('external_id_constraint_2') (user_id, external_id)
Operations:
Add external id
Adding an new external id for user 1 it would look like this:
insert into external_ids (user_id, external_id, disabled_by) values ('user1', 'exid2', '');
Disabling an external id
If the external id is later revoked for user 1:
update external_ids set disabled_by='admin1' where user_id='user1' and external_id='exid2';
Reenabling the external_id
A user can't have more than 1 entry for a given external_id. If a row exists ('user1', 'exid2', 'admin1') then the row needs to be updated:
update external_ids set disabled_by='' where user_id='user1' and external_id='exid2';
Rather than a new row being created. However another user between the disable and the reenable attempt could have claimed the external_id. If this has happened the update should do nothing.
Solutions attempted
I am trying to get a single postgres sql statement to handle this case.
Things I tried:
- an insert into .... on conflict on constraint ... except that I need to handle 2 different constraint violations differently.
- update does not have the ability to do the insert if there is nothing to update
- update doesn't have the ability to handle a constraint violation.
Question:
Is it possible to do this in a single sql statement or am I doomed to be frustrated.
postgresql
asked 5 mins ago
PatPat
1011
New contributor
Pat is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I have a table that has these key columns. Other columns are present but these are the key columns for this question.
user_id: string,
external_id: string
disabled_by: string
Additional notes:
- All columns have the not null constraint.
- unique constraint ('external_id_constraint_1') (external_id, disabled_by)
- unique constraint ('external_id_constraint_2') (user_id, external_id)
Operations:
Add external id
Adding an new external id for user 1 it would look like this:
insert into external_ids (user_id, external_id, disabled_by) values ('user1', 'exid2', '');
Disabling an external id
If the external id is later revoked for user 1:
update external_ids set disabled_by='admin1' where user_id='user1' and external_id='exid2';
Reenabling the external_id
A user can't have more than 1 entry for a given external_id. If a row exists ('user1', 'exid2', 'admin1') then the row needs to be updated:
update external_ids set disabled_by='' where user_id='user1' and external_id='exid2';
Rather than a new row being created. However another user between the disable and the reenable attempt could have claimed the external_id. If this has happened the update should do nothing.
Solutions attempted
I am trying to get a single postgres sql statement to handle this case.
Things I tried:
- an insert into .... on conflict on constraint ... except that I need to handle 2 different constraint violations differently.
- update does not have the ability to do the insert if there is nothing to update
- update doesn't have the ability to handle a constraint violation.
Question:
Is it possible to do this in a single sql statement or am I doomed to be frustrated.
postgresql
asked 5 mins ago
PatPat
1011
New contributor
Pat is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I have a table that has these key columns. Other columns are present but these are the key columns for this question.
user_id: string,
external_id: string
disabled_by: string
Additional notes:
- All columns have the not null constraint.
- unique constraint ('external_id_constraint_1') (external_id, disabled_by)
- unique constraint ('external_id_constraint_2') (user_id, external_id)
Operations:
Add external id
Adding an new external id for user 1 it would look like this:
insert into external_ids (user_id, external_id, disabled_by) values ('user1', 'exid2', '');
Disabling an external id
If the external id is later revoked for user 1:
update external_ids set disabled_by='admin1' where user_id='user1' and external_id='exid2';
Reenabling the external_id
A user can't have more than 1 entry for a given external_id. If a row exists ('user1', 'exid2', 'admin1') then the row needs to be updated:
update external_ids set disabled_by='' where user_id='user1' and external_id='exid2';
Rather than a new row being created. However another user between the disable and the reenable attempt could have claimed the external_id. If this has happened the update should do nothing.
Solutions attempted
I am trying to get a single postgres sql statement to handle this case.
Things I tried:
- an insert into .... on conflict on constraint ... except that I need to handle 2 different constraint violations differently.
- update does not have the ability to do the insert if there is nothing to update
- update doesn't have the ability to handle a constraint violation.
Question:
Is it possible to do this in a single sql statement or am I doomed to be frustrated.
postgresql
postgresql
asked 5 mins ago
PatPat
1011
New contributor
Pat is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 5 mins ago
PatPat
1011
New contributor
Pat is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 5 mins ago
PatPat
1011
New contributor
Pat is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 5 mins ago
PatPat
1011
asked 5 mins ago
PatPat
1011
1011
New contributor
Pat is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Pat is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Pat is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Pat is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f232934%2fpostgres-complex-insert-or-update-with-2-unique-constraints%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Pat is a new contributor. Be nice, and check out our Code of Conduct.
Pat is a new contributor. Be nice, and check out our Code of Conduct.
Pat is a new contributor. Be nice, and check out our Code of Conduct.
Pat is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f232934%2fpostgres-complex-insert-or-update-with-2-unique-constraints%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
