asked on sql if
Hi i need one ANSWER?
HOW TO CHECK IF THERE IS SOMETHING IN VALUE USER:
if (@USER=NULL OR @USER='0') then
ALTER TABLE [TABLE] NOCHECK CONSTRAINT [FK_TABLE_USER]
IF THEN DOESN'T WORK
thx
HOW TO CHECK IF THERE IS SOMETHING IN VALUE USER:
if (@USER=NULL OR @USER='0') then
ALTER TABLE [TABLE] NOCHECK CONSTRAINT [FK_TABLE_USER]
IF THEN DOESN'T WORK
CREATE PROCEDURE [dbo].[TABLE_INSERT]
(
@NAME varchar(3),
@USER varchar(3),
)
AS
BEGIN
SET NOCOUNT ON;
BEGIN TRY
if (@USER=NULL OR @USER='0') then
ALTER TABLE [TABLE] NOCHECK CONSTRAINT [FK_TABLE_USER]
-- Insert statements for procedure here
INSERT INTO [TABLE]
([NAME]
,[USER]
VALUES
(@NAME,
@USER) )
END TRY
END
thx
Microsoft SQL ServerMicrosoft SQL Server 2008
Last Comment
Scott Pletcher
What do you mean "doesn't work"?
Did the INSERT fail when you expected it to succeed?
Did the ALTER TABLE statement fail?
Did the INSERT fail when you expected it to succeed?
Did the ALTER TABLE statement fail?
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
You can't use "= NULL", you must use IS NULL:
if (@USER IS NULL OR @USER='0')
if (@USER IS NULL OR @USER='0')
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Actually you said use one "or" the other.
ONLY the version with IS NULL is correct and works.
ONLY the version with IS NULL is correct and works.
"does not work" and "does not do the right thing" is different :)
if (@user=null)
... do something here
end;
above code is correct but the code inside never works since that condition gives false...
the original code posted by author gives syntax error :) So, I fixed syntax first, then gave the correct logical code :) combo...
if (@user=null)
... do something here
end;
above code is correct but the code inside never works since that condition gives false...
the original code posted by author gives syntax error :) So, I fixed syntax first, then gave the correct logical code :) combo...
>> "does not work" and "does not do the right thing" is different :) <<
Not necessarily. Colloquially then can mean the same thing.
Not necessarily. Colloquially then can mean the same thing.
probably you forgot to end if . you should do something like this:
...
BEGIN
var := var + 1;
IF var = 100 THEN
var := 0;
COMMIT;
END IF;
...