Question on storing non english character
From: Pap <oracle.developer35_at_gmail.com>
Date: Wed, 25 Aug 2021 19:40:20 +0530
Message-ID: <CAEjw_fih4KOvE9S6S9QEz8Pw9V5p02_kgLPWJL9KVDsGQOSfOQ_at_mail.gmail.com>
Hello Listers, We are getting some requirements in which many of the attributes in our database may need to cater to non english/multi byte characters. Currently we have the defaults setup as bytes at the database level. Which means if we create any attribute with varchar2(N) it defaults to varchar2(N bytes). And existing attributes are defined the same way , say e.g varchar2(N bytes). so they have to be varchar2(N char) to work without fail.
Date: Wed, 25 Aug 2021 19:40:20 +0530
Message-ID: <CAEjw_fih4KOvE9S6S9QEz8Pw9V5p02_kgLPWJL9KVDsGQOSfOQ_at_mail.gmail.com>
Hello Listers, We are getting some requirements in which many of the attributes in our database may need to cater to non english/multi byte characters. Currently we have the defaults setup as bytes at the database level. Which means if we create any attribute with varchar2(N) it defaults to varchar2(N bytes). And existing attributes are defined the same way , say e.g varchar2(N bytes). so they have to be varchar2(N char) to work without fail.
My question is , if there exists any downside if we set it(CHAR) as default at the database level? or say by default create all the new table columns as VARCHAR2(N CHAR)?
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Aug 25 2021 - 16:10:20 CEST