Attempting to insert into a table with an SQL trigger using 1.4 will result in database engine error 334. about mssql-django HOT 8 OPEN

Just to be sure, explicitly setting it to False has not resolved the issue.

from mssql-django.

HI there, we're able to reproduce this locally and are investigating.

from mssql-django.

This is due to a change on our end. As a workaround, can you try adding "OPTIONS": {"return_rows_bulk_insert": False} to your options?

from mssql-django.

I tried but the situation remained the same and the same error occurred.

DATABASES = {
    "default": {
        "ENGINE": "mssql",
        "NAME": "db",
        "USER": "user",
        "PASSWORD": "password",
        "HOST": "localhost",
        "PORT": "1433",
        "OPTIONS": {
            "driver": os.getenv("MSSQL_DRIVER", "ODBC Driver 18 for SQL Server"),
            "return_rows_bulk_insert": False,
            "extra_params": "",
        },
    }
}

The default value is False, so it was already False when I first reported it.

from mssql-django.

The default was changed to true for 1.4 but we are planning to change it back

from mssql-django.

Having a similar issue with:

Django: 5.0.3
mssql-django: 1.4
python: 3.11.6

The target table 'xxxxxxxxxx' of the DML statement cannot have any enabled triggers if the statement contains an OUTPUT clause without INTO clause. (334) (SQLExecDirectW);

Have tried setting return_rows_bulk_insert to True and False, neither worked. Cannot roll back to 1.3 as it doesn't support Django 5.

I can confirm that running 4.2.11 & mssql-django 1.3 does not have this issue.

from mssql-django.

Same issue appearing in my side as well with mssql-django: 1.4

SQL Trigger for 'AFTER INSERT' fails with the same error

[SQL Server]The target table 'xxxxxxxxxxxx' of the DML statement cannot have any enabled triggers if the statement contains an OUTPUT clause without INTO clause.

from mssql-django.

Same issue here with. I'm using mssql-django: 1.4

from mssql-django.