July 17, 2015 at 6:04 pm
Use stored procedures for CRUD operations, and include code in there to update the header.
The problem I have with triggers, is that people/tools don't always remember to check for them before dropping a table and recreating it with new/modified columns/constraints. ( I work a lot with systems where the standard support response is to suggest a dump/drop/reload, so have dealt with this a lot :angry: )
Of course, you could create a database or server ddl trigger that monitors for table drops/creation and recreates your dml triggers, but it's much easier and safer to use stored procedures in my opinion.
But, however you choose to implement it, I agree with the sentiment "In the database" 🙂
MM
select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);
Viewing post 16 (of 15 total)
You must be logged in to reply to this topic. Login to reply