Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Fred Goldbach (FredG487)
Highmark Health
Fred Goldbach
Highmark Health
US
FredG487 Member since 2009 38 posts
Highmark Health
Posted: Nov 2, 2018
Last activity: Nov 15, 2018
Posted: 2 Nov 2018 10:55 EDT
Last activity: 15 Nov 2018 12:52 EST
Closed

Pega 8.1 Database DDL Changes - CHAR vs. BYTE

Hello! In looking at Pega 8.1, we noticed some differences with the DDL. The issue is with the way columns are defined. In Pega 7.x, the column was defined as - pxcoverinskey varchar2(255 BYTE). In Pega 8.1, the same column is defined - pxcoverinskey varchar2(255 CHAR).

Is this going to pose any issues with upgrades where the tables are defined differently?

***Edited by Moderator Marissa to update platform capability tags****

To see attachments, please log in.
Data Integration
Updates

  • uday puli Jamuna Ramalingam SNEHA LATHA JUPALLI
Posted: 6 years ago
Posted: 15 Nov 2018 12:52 EST
Jie Long (LONGJ)
PEGA
Fellow, Software Architect, Services Engineering
Pegasystems Inc.
US

No issue for upgrade. Supporting new column with 'char' semantics is to help address some multi-byte char issue. Upgrade won't change existing text columns' semantics.  

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice