Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Other: make the trimming of trailling characters configurable/optional

Completed
Pablo Vivanco User

We opened case 110720 about the issue of HVR trimming trailling spaces when the source is a char(n) or nchar(n).  When the target is a database such as Snowflake, the trailling characters are not put back, thus resulting in a data change/inconsistency.

 

The request is that when we add a table tp a channel, we have the ability to signify whether or not we want/need the trailling characters trimmed.

 

Thanks,

 

Pablo Vivanco

Data Solutions Distinguished Architect | Enterprise Data Office

Edwards Lifesciences LLC | www.edwards.com

Office 949.250.2324 | Cell  949.246.3857 | Skype (949) 508-0335

 

 

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Official comment
    Mark Van de Wiel User

    Pablo,

    We changed default trimming to no longer do this in HVR 6.1 (and following) as part of RD-308390.

    Hope this helps.
    Mark.