Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: proposal casting from XML[] to int[], numeric[], text[]
- From: Peter Eisentraut <peter_e(at)gmx(dot)net>
- To: "Nikolay Samokhvalov" <nikolay(at)samokhvalov(dot)com>
- Cc: pgsql-hackers(at)postgresql(dot)org, "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>
- Subject: Re: proposal casting from XML[] to int[], numeric[], text[]
- Date: Mon, 8 Oct 2007 12:53:38 +0200
Am Freitag, 28. September 2007 schrieb Nikolay Samokhvalov: > what should be returned for XML like "<em><strong>PostgreSQL</strong> > is a powerful, open source relational database system</em>" if user > requests for text under "em" node? In XML world, the correct answer is > "PostgreSQL is a powerful, open source relational database system" -- > concatenation of all strings from the node itself and all its > descendants, in the correct order. Will be this expected for RDBMS > users?). Well, if that is the defined behavior for XPath, then that's what we should do. -- Peter Eisentraut http://developer.postgresql.org/~petere/
- Follow-Ups:
- Re: proposal casting from XML[] to int[], numeric[], text[]
- From: Andrew Dunstan
- Re: proposal casting from XML[] to int[], numeric[], text[]
- Prev by Date: Re: Including Snapshot Info with Indexes
- Next by Date: Re: Including Snapshot Info with Indexes
- Previous by thread: Including Snapshot Info with Indexes
- Next by thread: Re: proposal casting from XML[] to int[], numeric[], text[]
- Indexes: