G'morn. I use COLUMNS-UPDATED on a couple of audit-type triggers to avoid having certain columns trigger the..erm..trigger. Working on my local db, I added a new column that I want mask. I look up the column_id. 37. Great. I tweak a few things, dropping then adding that column until I like my code. Then I notice that the column_id has increased with each drop/add. Now it is at 40.
Not a problem. Except my COLUMNS-UPDATED mask for column_id 40 won't be applicable to production, where the added column will have an ID of 37.
So. Bleary-eyed early morning complexities make me ramble. But can I:
"reset" the column_id increment of a table, so it will be sure to always assign ([last existing column_id + 1]), OR
assign the column_id at the time I create a column?
*slogs off in search of more coffee*