Why am I getting the error “non-boolean type specified in a context where a condition is expected” for...
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I am getting this error :"Error 102 : non-boolean type specified in a context where a condition is expected"
for this request :
DECLARE @num_dossiers TABLE (num_dossier INT,indice NVARCHAR(3))
insert into @num_dossiers
select num_dossier,indice from dossier where num_sec=57
delete from constitue where (num_dossier,indice) in select (num_dossier,indice) from @num_dossiers
The request triggering the error is the last one :
delete from constitue where (num_dossier,indice) in select (num_dossier,indice) from @num_dossiers
What could be the cause of this error ?
sql-server sql-server-2008
add a comment |
I am getting this error :"Error 102 : non-boolean type specified in a context where a condition is expected"
for this request :
DECLARE @num_dossiers TABLE (num_dossier INT,indice NVARCHAR(3))
insert into @num_dossiers
select num_dossier,indice from dossier where num_sec=57
delete from constitue where (num_dossier,indice) in select (num_dossier,indice) from @num_dossiers
The request triggering the error is the last one :
delete from constitue where (num_dossier,indice) in select (num_dossier,indice) from @num_dossiers
What could be the cause of this error ?
sql-server sql-server-2008
add a comment |
I am getting this error :"Error 102 : non-boolean type specified in a context where a condition is expected"
for this request :
DECLARE @num_dossiers TABLE (num_dossier INT,indice NVARCHAR(3))
insert into @num_dossiers
select num_dossier,indice from dossier where num_sec=57
delete from constitue where (num_dossier,indice) in select (num_dossier,indice) from @num_dossiers
The request triggering the error is the last one :
delete from constitue where (num_dossier,indice) in select (num_dossier,indice) from @num_dossiers
What could be the cause of this error ?
sql-server sql-server-2008
I am getting this error :"Error 102 : non-boolean type specified in a context where a condition is expected"
for this request :
DECLARE @num_dossiers TABLE (num_dossier INT,indice NVARCHAR(3))
insert into @num_dossiers
select num_dossier,indice from dossier where num_sec=57
delete from constitue where (num_dossier,indice) in select (num_dossier,indice) from @num_dossiers
The request triggering the error is the last one :
delete from constitue where (num_dossier,indice) in select (num_dossier,indice) from @num_dossiers
What could be the cause of this error ?
sql-server sql-server-2008
sql-server sql-server-2008
asked yesterday
mounaimmounaim
3263723
3263723
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
SQL Server doesn't support a multi-column IN clause (unlike Oracle).
delete
from constitue
where (num_dossier,indice) in select (num_dossier,indice) from @num_dossiers
This can be rewritten as a EXISTS:
DELETE c
FROM constitue c
WHERE EXISTS
(SELECT 1 FROM @num_dossiers nd WHERE n.num_dossier = c.num_dossier AND n.indice = c.indice);
this was helpful, Thank you sir :) Any idea on why SQL Server does not support this kind of IN syntax? the Oracle style seems more intuitive
– mounaim
yesterday
1
You can express support for this (currently unplanned) prospect here: feedback.azure.com/forums/908035-sql-server/suggestions/…
– Peter Vandivier
yesterday
add a comment |
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
});
}
});
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%2f234938%2fwhy-am-i-getting-the-error-non-boolean-type-specified-in-a-context-where-a-cond%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
SQL Server doesn't support a multi-column IN clause (unlike Oracle).
delete
from constitue
where (num_dossier,indice) in select (num_dossier,indice) from @num_dossiers
This can be rewritten as a EXISTS:
DELETE c
FROM constitue c
WHERE EXISTS
(SELECT 1 FROM @num_dossiers nd WHERE n.num_dossier = c.num_dossier AND n.indice = c.indice);
this was helpful, Thank you sir :) Any idea on why SQL Server does not support this kind of IN syntax? the Oracle style seems more intuitive
– mounaim
yesterday
1
You can express support for this (currently unplanned) prospect here: feedback.azure.com/forums/908035-sql-server/suggestions/…
– Peter Vandivier
yesterday
add a comment |
SQL Server doesn't support a multi-column IN clause (unlike Oracle).
delete
from constitue
where (num_dossier,indice) in select (num_dossier,indice) from @num_dossiers
This can be rewritten as a EXISTS:
DELETE c
FROM constitue c
WHERE EXISTS
(SELECT 1 FROM @num_dossiers nd WHERE n.num_dossier = c.num_dossier AND n.indice = c.indice);
this was helpful, Thank you sir :) Any idea on why SQL Server does not support this kind of IN syntax? the Oracle style seems more intuitive
– mounaim
yesterday
1
You can express support for this (currently unplanned) prospect here: feedback.azure.com/forums/908035-sql-server/suggestions/…
– Peter Vandivier
yesterday
add a comment |
SQL Server doesn't support a multi-column IN clause (unlike Oracle).
delete
from constitue
where (num_dossier,indice) in select (num_dossier,indice) from @num_dossiers
This can be rewritten as a EXISTS:
DELETE c
FROM constitue c
WHERE EXISTS
(SELECT 1 FROM @num_dossiers nd WHERE n.num_dossier = c.num_dossier AND n.indice = c.indice);
SQL Server doesn't support a multi-column IN clause (unlike Oracle).
delete
from constitue
where (num_dossier,indice) in select (num_dossier,indice) from @num_dossiers
This can be rewritten as a EXISTS:
DELETE c
FROM constitue c
WHERE EXISTS
(SELECT 1 FROM @num_dossiers nd WHERE n.num_dossier = c.num_dossier AND n.indice = c.indice);
answered yesterday
Mark SinkinsonMark Sinkinson
8,03633049
8,03633049
this was helpful, Thank you sir :) Any idea on why SQL Server does not support this kind of IN syntax? the Oracle style seems more intuitive
– mounaim
yesterday
1
You can express support for this (currently unplanned) prospect here: feedback.azure.com/forums/908035-sql-server/suggestions/…
– Peter Vandivier
yesterday
add a comment |
this was helpful, Thank you sir :) Any idea on why SQL Server does not support this kind of IN syntax? the Oracle style seems more intuitive
– mounaim
yesterday
1
You can express support for this (currently unplanned) prospect here: feedback.azure.com/forums/908035-sql-server/suggestions/…
– Peter Vandivier
yesterday
this was helpful, Thank you sir :) Any idea on why SQL Server does not support this kind of IN syntax? the Oracle style seems more intuitive
– mounaim
yesterday
this was helpful, Thank you sir :) Any idea on why SQL Server does not support this kind of IN syntax? the Oracle style seems more intuitive
– mounaim
yesterday
1
1
You can express support for this (currently unplanned) prospect here: feedback.azure.com/forums/908035-sql-server/suggestions/…
– Peter Vandivier
yesterday
You can express support for this (currently unplanned) prospect here: feedback.azure.com/forums/908035-sql-server/suggestions/…
– Peter Vandivier
yesterday
add a comment |
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%2f234938%2fwhy-am-i-getting-the-error-non-boolean-type-specified-in-a-context-where-a-cond%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