Eric.Jones wrote:
Serge Rielau wrote: ZD-Net article:
http://news.zdnet.com/2100-9593_22-6057835.html Download:
http://www.ibm.com/software/data/db2..._download.html
Docs: http://publib.boulder.ibm.com/infoce...w/v9/index.jsp
Enjoy Serge
Thanks for the interesting links on v9 ...
From reading the publib doc: Tutorial for native XML data store
"You can create tables with XML columns only in databases defined with
the UTF-8 code set and a
compatible territory code."
But looking through the migration task(s), there is no mention of
changing DB code sets.
What is the envisioned method to enable XML features into existing DB2
v8 sites?
Should a hybrid dual-DB configuration be employed, or better to first
migrate v8 DBs to UTF-8 code set?
The strategy as I see it right now is to move to UTF-8 in the long haul.
Migration (I prefer the word upgrade myself) typically involves enabling
a DB on an old release to a new release without exploiting new features.
That's why you will find no mention in the docs on UTF-8 due to XML.
If you have existing DBs and you cannot/want not move them to UTF-8 at
this time, yet you want to start exploiting XML I would look into a
separate DB indeed.
For new applications starting of in UTF-8 may be in order.
In a future version I'd expect that a unicode db will provide a superset
of the capabilities as non-unicode and a whole sale move to UTF-8 will
be recommended in it's own right (with or without XML as added incentive)
Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab