Hi all - I am using the SQL server connector to integrate with my existing db and I am getting the error below when running prisma.{table}.create. It seem this is an issue with SQL server and the use of OUTPUT along with a trigger. Is there a workaround for this, or plans to support triggers in future release? By the way, when I remove the trigger the create statement works.

(node:37320) UnhandledPromiseRejectionWarning: Error: 
Invalid `prisma.formSets.create()` invocation:


  Error occurred during query execution:
ConnectorError(ConnectorError { user_facing_error: None, kind: QueryError(TokenError { code: 334, state: 1, class: 16, message: "The target table \'dbo.FormSetSequence\' of the DML statement cannot have any enabled triggers if the statement contains an OUTPUT clause without INTO clause.", server: "dev-dfleming", procedure: "", line: 1 }) })
    at PrismaClientFetcher.request (C:\dev\graph-ql-prisma-ta\node_modules\@prisma\client\runtime\index.js:78786:15)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:37320) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see <https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode>). (rejection id: 3)
(node:37320) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

oh, yeah, let's write here too: this is a bug, we don't support triggers yet. I'm currently fixing it and expect a fix in the release after this in 2.14.0