Hi @wouter.goslinga
I will see if I can get an answer of this.
Are you using a new/different database that has a case sensitive collation?
No, only change is upgrade TX from 6645 to 6675
Hi @wouter.goslinga
You can make it work by matching the cases, right?
Besides that, it seems to be a consequence of changing the SQLClient.
@Thomas Lind correct, if the cases match it works again. We did indeed update the TX SQL Client to the latest version, so that could very well be the case.
Maybe, if this is by design / not a bug, this should be listed as a warning in the release notes because it can possibly break execution without notice in advance.
Hi,
the collation of your database (or table or column for data) should decide case sensitivity. If your collation has CS then that should always result in those kind of issues, CI should not. Snowflake has this for instance.
TimeXtender should not be adding case sensitivity for systems that are not without explicitly notifying users of such a change, in my opinion. Of course, if you decide to move to something like Snowflake or a CS collation on your SQL infrastructure, you would need to refactor all your custom SQL.
@Thomas Lind correct, if the cases match it works again. We did indeed update the TX SQL Client to the latest version, so that could very well be the case.
Maybe, if this is by design / not a bug, this should be listed as a warning in the release notes because it can possibly break execution without notice in advance.
Hi @wouter.goslinga
It is a bug, I just wanted to know if you could continue.
It will be fixed in a future hotfix release.
@wouter.goslinga a fix for this has now been released in
