An error occurred with OUTPUT clause when a trigger is on the table

[mikilion]

Chain commands as Insert, Update or Delete with return value generate a error when a trigger is on the table:

The target table 'TableName' of the DML statement cannot have any enabled triggers if the statement contains an OUTPUT clause without INTO clause

[Grauenwolf]

Can you show me the line of code you used to trigger this error?

I think I know how to fix it, but I want to make sure I address your specific use case.

[Grauenwolf]

And just to verify, are you using SQL Server?

[mikilion]

The error occur by Chain commands as these:

dataSource.Upsert("TableName", entity).WithRefresh()...
dataSource.Insert("TableName", entity).ToInt32()...
dataSource.Insert("TableName", entity).ToObject()...

I'm using SQL Server 2016.

[Grauenwolf]

Dev notes.

1. Detect tables with triggers: select * from sys.triggers
2. If they exist, switch to using a temp table in the SQL generation as per http://stackoverflow.com/questions/13198476/cannot-use-update-with-output-clause-when-a-trigger-is-on-the-table

[mikilion]

Why not provide an option to specify when to use a temporary table?

[Grauenwolf]

I can provide a behavior override as an advanced feature, but it really should "just work" regardless if you have triggers or not. Otherwise adding a trigger to a pre-existing table becomes a breaking change.

[Grauenwolf]

Inserts are now fixed. But they require a change to the Core library, so it won't be published until version 1.1.

Still need to port the fix update, delete, and maybe upsert.

[Grauenwolf]

Update/Delete are done. Confirmed that Upsert has the same bug.

[Grauenwolf]

This feature will be part of this week's Chain 1.1. release.