Mike writes
I've been trying to decipher some MSSQL stored procs with a view to
converting to Ingres stored procs.

At the customer site where I spend a lot of time these days, there is a
module which deals with 100s of transactions per second - each transaction
described by XML. The module, written in VB.net, makes heavy use of MSSQL
stored procedures which in turn use sp_xml_preparedocument and
sp_xml_removedocument.
http://msdn.microsoft.com/en-us/library/ms187367.aspx

One procedure's job seems to be to take a bit of XML as a parameter,
deconstruct the XML into a temp table with one row per attribute, extract
the text value of one of those attributes then use that to update the DB.

You can guess which server in the network is severely overloaded on busy
days.

On Apr 25, 2:56*pm, Roy Hann <specia... (AT) processed (DOT) almost.meat> wrote:
You mean "universal" in the meaning of "British Empire wide"?

Many of the world's languages use more than 1 byte (or even only 7
bits - what ASCII is) for a character, beware of the whole
universe .

Just consider a patch containing a fix for a bug involving some
international characters -
you wouldn't find these characters in the release notes coded as ASCII
text file.

So, using some unicode encoded file (e.g. in utf-8) is not a bad idea
- but it has not to be HTML.