a delete statement, followed by a create index statement, in the same query, will not throw a CF exception, if the index creation fails. Not sure if lucee bug, jdbc bug, or expected behavior. repro for anyone having an mssql setup:

transaction {
	try {
		queryExecute("
			create table RMME_FOO (id int);
			insert into RMME_FOO (id) values (1), (1), (1), (1); -- comment this out to cause the index creation to succeed
		")
		v = queryExecute("
			delete top (1) from RMME_FOO;
			create unique index RMME_FOO_UNIQUE_BY_ID on RMME_FOO (id);
		")
		
		writedump(v); // no error ??
		
		idx = queryExecute("
			select * from sys.indexes where name = N'RMME_FOO_UNIQUE_BY_ID'
		")
		
		writedump(idx); // nothing, index creation failed because there were duplicates
	}
	finally {
		transaction action="rollback";
	}
}

And a freaking annoying one at that

Looking for the ticket

Yeah, it can create some VERY HARD TO TRACK bugs in your code 😕

I'm not sure why @micha end up hiding my fixes behind the feature flag, but we've been using my fixes for almost a year without incident.