objects to be treated separately
when i edit a trigger i would like to check in the trigger changes only, not the entire table changes, contraints, etc as i may not have finished with them
Sean Lynch commented
I would like them separate because it makes merging between branches easier. If two different triggers on the same table change, each in different branches if they were separate there would be no merge issues. With it all in a single file we will often need to manually merge the two files.
yes this is an idea we'd like to see as well. I think you're extended all table objects, thus indexes would be selectable as well just like other objects (procs, views, etc)
I agree that triggers should be autonomous and not linked to their parent object.
@Greg - this is for DDL triggers. As a DML trigger is dependent on its parent table, it was deemed appropriate to keep them together. However, there are many reasons why it makes sense to separate them, so it's something we'll be considering going forward.
SQLSC actually makes a "database triggers" directory -- it should really put the triggers into that.