Replicated table DDL - control column name casing

Completed

Follow

1

Artashes Hovasapyan

• October 16, 2019 08:13

It would be really nice to have more control over the replicated tables' DDL. For example lowercasing all the column names eventually results in need to add additional double quotes around column names. Ideally this would be something to control upon replication job creation.

• Comment actions Permalink

  Official comment

  

  Salvatore Raunich

  • October 17, 2019 18:41

  Hi Artashes,

  thanks for posting your feature request to our online community.

  The main reason why all the column names of materialized or replicated tables are in lowercase is to keep our table and column name generation algorithm as generic as possible. Data Virtuality supports different analytical and target storage and in order to avoid potential incompatibilities between different data sources, we remove special characters and convert the final names in lowercase.

  We understand that different databases also have different default lower/uppercase for identifiers and for this reason we are implementing the possibility to control, at data source level, if column names should be all in lower or uppercase.

  This improvement is already in QA and will be released in one of the next minors.

  Do you think that this will improve the usability on your side and solve your specific problem?

  Best

  Salvatore

• 0

  Comment actions Permalink

  

  Artashes Hovasapyan

  • November 05, 2019 16:18

  Hello Salvatore,

  I think if the column names of the replicated table would driven by the definition of the view that is being replicated, and, as possible addition, an optional parameter to switch back to lowercase column names in SYSADMIN.batchUpdate and other similar replication/materialization procedures, it would be a very good improvement.

  Regards,
  Artashes

• 0

  Comment actions Permalink

  

  Salvatore Raunich

  • November 11, 2019 18:15

  Hello Artashes,

  I discussed internally with developers and we will extend the current implementation by giving the possibility to preserve the casing of column names, based on the original table/view definitions. This will be configurable at data source level. 

  We are planning to include this in one of the next 2.1 minor releases and in the upcoming 2.3.

  I will keep you updated here.

  Best

  Salvatore

• 0

  Comment actions Permalink

  

  Niklas Schmidtmer

  • December 20, 2019 10:54
  • Edited

  Hi Artashes,

   

  we now released this feature as part of the version 2.1.26. Please reach out to our support team if you would like to schedule an update or receive a patch.

   

  Best

   

  Niklas

• 0

  Comment actions Permalink

  

  Artashes Hovasapyan

  • March 12, 2020 10:49

  Hello Niklas,

   

  Can you please point me to the documentation for this feature? I've just upgraded to version 2.3.2 and cannot find where can this be configured.

   

  Regards,

  Artashes

   

• 0

  Comment actions Permalink

  

  Niklas Schmidtmer

  • March 12, 2020 12:02

  Hi Artashes,

   

  the relevant page in the documentation is the Translators section. The parameter is called columnNameType. You can apply it by editing a data source and adding the parameter to the Translator parameters input field (e.g. columnNameType=UPPERCASE).

   

  Best

   

  Niklas

Please sign in to leave a comment.