How to get tablea, ID in without enter tableb E_ID. Tablea ID how reflect in tableb E_ID

Question

0.00/5 (No votes)

See more:

i have created two tables in SQL Database

TableA: Columns Names; ID, Name;
TableB: Columns Names: E_Id, DOB;

TableA: ID primary KEY, TableB: E_Id Foreign KEY

TableA ID		Name
		1		AAAA
		2		BBBB

how to reflect TableA of ID Second TableB of E_ID

TableB E_ID 	DOB
				12/12/1998
				15/09/1994

only Insert ID in TableA. whenever Enter ID in TableA, at the same time
how to reflect E_ID in TableB.

after that reflect TableB in E_ID

how to get this OUTPUT

TableB E_ID 	DOB
		1		12/12/1998
		2		15/09/1994

now TableA ID and TableB E_ID are SAME.

What I have tried:

SQL

SELECT * INTO TableB
FROM TableA
WHERE ID IN
(SELECT ID FROM TableB)

Posted 1-Jan-22 3:55am

2011999

Updated 1-Jan-22 5:55am

PIEBALDconsult

v2

Add a Solution

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 · 2022-01-01T04:22:00

Foreign keys are there to enforce referential integrity and you can't have that unless the appropriate row already exists in the other table.

It's like an invoice: you have one invoice which has the (legally required) invoice number and date, the customer information, the total item cost, the delivery charges, the taxes, and the total to be paid.
There are also the invoice lines, each of which refers to a specific invoice, and holds the details for one purchase item: the number of product units involved, the product type and description, the unit price, the line total.

You can't create the in voice lines without first creating the invoice as they would not have anything to refer to, so you create the invoice first, then add the line items to it.

What you have is done the same way: the TableA row is created first, then the ID for that is used when the TableB rows are created.

And if I'm honest, there doesn't seem to be any good reason why you would split the tables that way: a person is born only once, so there is no reason for keeping the DOB in a separate table from the person's name.