Re: CLOB issue with JDBC, IBATIS and Oracle 10g
- From: David Harper <devnull@xxxxxxxxxxxxxxxxxxx>
- Date: Mon, 24 Sep 2007 18:32:23 GMT
RedGrittyBrick wrote:
Roedy Green wrote:On Sat, 22 Sep 2007 09:57:56 -0400, Lew <lew@xxxxxxxxxxxxx> wrote, quoted or indirectly quoted someone who said :
Small nit: the number of bytes per char is variable, depending on
the database's encoding.
In a pathological case UTF-8 can take 3 bytes per char.
UTF-8 takes *four* octets for a code point outside Unicode's base plane. For example the cuneiform numeric sign three sharu (U+1242E) is
F0 92 90 AE
How wonderfully ironic that there's a Unicode block (and a UTF-8 encoding!) devoted to the cuneiform script, a data storage format that remains readable almost five thousand years after it was invented.
How many of our databases will still be readable in 7000 AD?
Thanks for sharing that. It made my day :-)
David Harper
Cambridge, England
.
- References:
- CLOB issue with JDBC, IBATIS and Oracle 10g
- From: kartechy
- Re: CLOB issue with JDBC, IBATIS and Oracle 10g
- From: Roedy Green
- Re: CLOB issue with JDBC, IBATIS and Oracle 10g
- From: Lew
- Re: CLOB issue with JDBC, IBATIS and Oracle 10g
- From: Roedy Green
- Re: CLOB issue with JDBC, IBATIS and Oracle 10g
- From: RedGrittyBrick
- CLOB issue with JDBC, IBATIS and Oracle 10g
- Prev by Date: Re: CLOB issue with JDBC, IBATIS and Oracle 10g
- Next by Date: JDBC/mysql error...
- Previous by thread: Re: CLOB issue with JDBC, IBATIS and Oracle 10g
- Next by thread: How to know columns names in Derby database table
- Index(es):
Relevant Pages
|
|
