使用反射从元数据类中获取属性属性(Using reflection to get property attributes from a metadata class)

 好吧，那里你有很多泡菜。 
 一方面，您需要在表上使用instead of insert触发器，但另一方面，您希望获得此触发器生成的标识返回到激活它的存储过程。 
 
 由于无法向触发器发送参数，因此您必须执行以下三种操作之一： 
 
 
 
 找到一些方法来消除对它的需要而不是触发器。 
 这是我最好的建议。 
 
 
 将存储过程分为两部分：一部分将执行所有操作，直到insert into语句（包括它），从而激活instead of insert触发器，以及另一部分将执行触发后所需的所有操作。 这样，您可以使用scope_identity() instead of insert触发器，并将其返回值作为参数发送到第二个存储过程。 
 注意：此设计意味着您必须逐个插入记录。 如果您尝试插入多条记录， scope_identity()将仅返回触发器插入的最后一行的标识。 
 
 
 找到一些在存储过程和而不是触发器之间传递数据的方法。 由于触发器不能除了或返回参数，因此您必须使用临时表或常规表。 建议的解决方案仅作为最后的手段，因为它会使您的代码复杂化，并可能导致一些性能问题。 此外，您必须找到一种方法来执行存储过程，直到触发器完成它的工作。 我可以给你一些关于如何在程序和触发器之间共享数据的指针，但我真的建议不要选择这个解决方案。 
 

Well, you've got yourself quite a pickle there.
 From the one hand, you need the instead of insert trigger on your table, but from the other hand, you want to get the identity that this trigger generates back to the stored procedure that activated it. 
 
Since there is no way to send parameters to and from triggers, you will have to do one of 3 things:
 
 
 
Find some way to eliminate the need for that instead of trigger.
 This is my best recommendation. 
 
 
Break your stored procedure to 2 parts: One part will do everything until the insert into statement (including it), thus activating the instead of insert trigger, and the other part that will do all operations needed after the trigger. this way you can use the scope_identity() inside the instead of insert trigger and send it's return value to the second stored procedure as a parameter.
 Note: this design means you have to insert records one by one. should you try to insert more then one record, scope_identity() will only return the identity of the last row inserted by the trigger.
 
 
Find some way of passing data between the stored procedure and the instead of trigger. Since triggers can't except or return parameters, you will have to use either a temporary table or a regular table. This suggested solution is only suggested as a last resort, since it will complicate your code and probably cause some performance issues as well. Also, you will have to find a way to hold execution of the stored procedure until the instead of trigger will finish it's work. I can give you some pointers on how to share data between the procedure and the trigger, but I really suggest not to choose this solution.