moving from en_US.819 to en_US.utf8
Posted in 2011
Topics: Data Types & Schema Design
Hi All We are planning to move from our DB from en_us.819 to en_us.utf8. We would like to know what impact does it hold its IDS 11.5. We want to have multibyte character support. We will have to move from char to nchar and carchar to nvarchar. Will there be any impact on anyother datatype. What precauations we should take. Regards Debadatta --90e6ba4769812c0654049e831e38
Hy, don´t forget the applications Char based variables, also check in Windows Apps additional ActiveX tools that may have been used if they can take the max possible UTF8 Size. M$ always tells that String/Char is UTF8 capable, but you never know until someone really uses the last character with foreign (and therefore real 2 Byte chars) letters in a text field or so. Joerg Volz ----------------------------------------------------------------------------- -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Debadatta Mishra Sent: Tuesday, March 15, 2011 11:46 AM To: ids@iiug.org Subject: moving from en_US.819 to en_US.utf8 [23088] Hi All We are planning to move from our DB from en_us.819 to en_us.utf8. We would like to know what impact does it hold its IDS 11.5. We want to have multibyte character support. We will have to move from char to nchar and carchar to nvarchar. Will there be any impact on anyother datatype. What precauations we should take. Regards Debadatta --90e6ba4769812c0654049e831e38 ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum. IT Handel und Beratung Jörg Volz Bernhard-Früh-Str. 7 77855 Achern GERMANY Tel: +49 (0)7841-681651 Fax: +49 (0)7841-681654 Mobil: +49 (0)170-2989757 VAT-ID: DE201383541 http://www.it-volz.de
Another thing is application is Java based and reporting application, so you can imagine we are mostly talking about reports labels and headers , margin details and all those stuff. Reading through existing IDS forum looks like finding out the length of such data variable would real pain. Is it true as you for printing reports these things are really critical for alignment and other stuff. not much idea though how it will impact from java side connection. Thanks & Regards Debadatta Mishra ph -+918015907520 On Tue, Mar 15, 2011 at 4:21 PM, Joerg Volz <joerg@it-volz.de> wrote: > Hy, > > don´t forget the applications Char based variables, also check in Windows > Apps > additional ActiveX tools that may have been used if they can take the max > possible UTF8 Size. M$ always tells that String/Char is UTF8 capable, but > you > never know until someone really uses the last character with foreign (and > therefore real 2 Byte chars) letters in a text field or so. > > Joerg Volz > > ----------------------------------------------------------------------------- > > -----Original Message----- > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of > Debadatta Mishra > Sent: Tuesday, March 15, 2011 11:46 AM > To: ids@iiug.org > Subject: moving from en_US.819 to en_US.utf8 [23088] > > Hi All > > We are planning to move from our DB from en_us.819 to en_us.utf8. > > We would like to know what impact does it hold > > its IDS 11.5. We want to have multibyte character support. We will have to > move from char to nchar and carchar to nvarchar. Will there be any impact > on > anyother datatype. > > What precauations we should take. > > Regards > Debadatta > > --90e6ba4769812c0654049e831e38 > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > IT Handel und Beratung Jörg Volz > Bernhard-Früh-Str. 7 > 77855 Achern > GERMANY > > Tel: +49 (0)7841-681651 > Fax: +49 (0)7841-681654 > Mobil: +49 (0)170-2989757 > > VAT-ID: DE201383541 > > http://www.it-volz.de > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --20cf30025da6dc3ad2049e835511