Re: Copying Values on Change?

[Phillip Ward]

Quote

I have one database with two tables.
We have table A where all my user information is stored.
And we have table B where I have some additional information.

No, you don't.
You have a second table, B, where you have some duplicated information taken from table A.
Duplicated data is either a sign of a poor design or deliberate data de-Normalisation.

Why do you need this data in a separate table?
If you want to access this data as a "separate" entity, consider creating a view on Table A that only selects these fields.

create view uniqueDataView as 
select id, unique 
from TableA ;

Regards, Phill W.