February 24, 2016 at 11:16 am
We cannot use extra columns in file.
Maybe the person or persons that made this decision and decided to put you as the implementer should take on the task themselves.
If table t3 is new then what could possibly be dependent on if there is a fear that something might break? If t3 is not new then perhaps it just does not fit the requirements. Another table (t4) in this case would be better.
I would guess that t3 is existing already and unknown things depend on it and the shop has a history of using SELECT * here and there.
----------------------------------------------------
February 24, 2016 at 1:31 pm
MMartin1 (2/24/2016)
We cannot use extra columns in file.
Maybe the person or persons that made this decision and decided to put you as the implementer should take on the task themselves.
If table t3 is new then what could possibly be dependent on if there is a fear that something might break? If t3 is not new then perhaps it just does not fit the requirements. Another table (t4) in this case would be better.
I would guess that t3 is existing already and unknown things depend on it and the shop has a history of using SELECT * here and there.
This is a great use for views... rename t3, add the columns, and put an updateable view on the table and name it "t3".
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 2 posts - 16 through 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply