Skip to main content
To homepage To homepage
Solved

Case sensitivity in custom table inserts after upgrade to 6675.1

wouter.goslinga
TimeXtender Xpert
Forum|alt.badge.img+2

After upgrading to TimeXtender 6675.1, we are experiencing some errors when executing custom table inserts. The error message is ‘The given ColumnMapping does not match up with any column in the source or destination’.

As it turns out, we have a few CTI's where the target column name was spelled with a capital letter when in fact the column name was with a lowercase or vice versa. This was never a problem but we had to correct this in the newest 6675 version. Has there been a change in where the CTI's target columns are now case sensitive?

Best answer by Thomas Lind

wouter.goslinga wrote:

@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.

View original
Did this topic help you find an answer to your question?

8 replies

Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Thomas Lind
  • Community Manager
  • 1070 replies
  • June 27, 2024

Hi @wouter.goslinga 

I will see if I can get an answer of this.

wouter.goslinga
1 person likes this
  • wouter.goslinga
    wouter.goslinga
R
Problem Solver
  • RLB
  • Problem Solver
  • 79 replies
  • June 27, 2024

Are you using a new/different database that has a case sensitive collation?

wouter.goslinga
TimeXtender Xpert
Forum|alt.badge.img+2
  • wouter.goslinga
  • Author
  • TimeXtender Xpert
  • 52 replies
  • June 27, 2024

No, only change is upgrade TX from 6645 to 6675

Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Thomas Lind
  • Community Manager
  • 1070 replies
  • June 27, 2024

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. 

wouter.goslinga
TimeXtender Xpert
Forum|alt.badge.img+2
  • wouter.goslinga
  • Author
  • TimeXtender Xpert
  • 52 replies
  • June 27, 2024

@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.

rory.smith
TimeXtender Xpert
Forum|alt.badge.img+7
  • rory.smith
  • TimeXtender Xpert
  • 687 replies
  • June 28, 2024

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.

wouter.goslinga
1 person likes this
  • wouter.goslinga
    wouter.goslinga
Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Thomas Lind
  • Community Manager
  • 1070 replies
  • Answer
  • June 28, 2024
wouter.goslinga wrote:

@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
1 person likes this
  • wouter.goslinga
    wouter.goslinga
Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

@wouter.goslinga a fix for this has now been released in

 

Reply


Most helpful members this week

Terms and ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings