Declare the scalar variable person_id

Question

1.00/5 (1 vote)

See more:

The code below keeps getting an error;

Go
Create PROC debo.PERSON_ID(
@ADMIS_ID INT= NULL,
@PERSON_ID INT(4)= NULL,
@DOCTOR_ID INT(4) = NULL,
@ADMIS_DATE DATE NOT NULL,
@DISCH_DATE DATE NOT NULL
AS
BEGIN
SET NOCOUNT ON

INSERT INTO HOSP_ADMIS ( ADMIS_ID, PERSON_ID, DOCTOR_ID, ADMIS_DATE,DISCH_DATE)

VALUES ( @ADMIS_ID, @PERSON_ID, @DOCTOR_ID,@ADMIS_DATE,
@DISCH_DATE);

END
GO

What I have tried:

Honestly, I’m trying different syntax but still clueless on how to fix the error. New to MySQL so it’s understandable but I’m stuck

Posted 11-Dec-21 22:34pm

Keke V

Updated 11-Dec-21 23:40pm

Add a Solution

Comments

Richard MacCutchan 12-Dec-21 7:18am

"The code below keeps getting an error;"
Suggestion 1: if you get an error then please show the exact error message and which line causes it.
Suggestion 2: make use of the documentation that is available at MySQL :: MySQL Documentation[^].

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2021-12-11T23:40:00

I'd start by changing names: you have three items with the same name "Person_id":

1) The stored procedure is called PERSON_ID
2) The parameter is called @PERSON_ID
3) The column is called PERSON_ID

Not only does that make life confusing for developers reading your code, it's confusing for the system as well. You could get round it by fully qualifying the column name, but using "PERSON_ID" for a procedure isn't particularly helpful (it gives no clue as to what the procedure does) so a better solution would be to change that. Perhaps calling it AddAdmissionRecord would both cure the problem and make it more useful?