You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I meet this concern again, when the names of the tables are well informed. After several tests I realized that it happened on the tables of joins with only two fields which form a primary key.
I note that the creation of update trigger on a table is performed only on non-key fields. There are none on these tables, which must be the source of the error.
Log line triggering the error:
"00139 PE_ENTRETIEN_ETAT_MergeUpdate": "CREATE TRIGGER IF NOT EXISTS " trMergeUpdate_PE_ENTRETIEN_ETAT \ "AFTER UPDATE OF ON " PE_ENTRETIEN_ETAT \ "BEGIN \ tUPDATE " PE_ENTRETIEN_ETAT = "old Row"; END; ",
The table creation script :
"CREATE TABLE [dbo].[PE_ENTRETIEN_ETAT](
[CLE_ENTRETIEN] varchar NOT NULL,
[CLE_ETAT] varchar NOT NULL,
[RowId] [uniqueidentifier] NULL DEFAULT (newid()),
[RowVer] [int] NOT NULL DEFAULT ((1))
) ON [PRIMARY]"
I am using version 3.2.15 with Microsoft SQL Server.
Do you have a solution?
The text was updated successfully, but these errors were encountered:
Hello,
I meet this concern again, when the names of the tables are well informed. After several tests I realized that it happened on the tables of joins with only two fields which form a primary key.
I note that the creation of update trigger on a table is performed only on non-key fields. There are none on these tables, which must be the source of the error.
Log line triggering the error:
"00139 PE_ENTRETIEN_ETAT_MergeUpdate": "CREATE TRIGGER IF NOT EXISTS " trMergeUpdate_PE_ENTRETIEN_ETAT \ "AFTER UPDATE OF ON " PE_ENTRETIEN_ETAT \ "BEGIN \ tUPDATE " PE_ENTRETIEN_ETAT = "old Row"; END; ",
The table creation script :
"CREATE TABLE [dbo].[PE_ENTRETIEN_ETAT](
[CLE_ENTRETIEN] varchar NOT NULL,
[CLE_ETAT] varchar NOT NULL,
[RowId] [uniqueidentifier] NULL DEFAULT (newid()),
[RowVer] [int] NOT NULL DEFAULT ((1))
) ON [PRIMARY]"
I am using version 3.2.15 with Microsoft SQL Server.
Do you have a solution?
The text was updated successfully, but these errors were encountered: