Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: BUG #3734: Invalid XML schema output.
- From: Michael Glaesemann <grzm(at)seespotcode(dot)net>
- To: Peter Eisentraut <peter_e(at)gmx(dot)net>
- Cc: pgsql-bugs(at)postgresql(dot)org, Harald Armin Massa <haraldarminmassa(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>
- Subject: Re: BUG #3734: Invalid XML schema output.
- Date: Fri, 23 Nov 2007 15:52:57 -0500
On Nov 23, 2007, at 12:30 , Peter Eisentraut wrote:
Am Freitag, 23. November 2007 schrieb Michael Glaesemann:It's because some browser *HTML* parsers that aren't fully XML compliant won't parse it correctlyYes, that is pretty much it, but that is obviously irrelevant nowadays and for us, especially. Some sources seem to use it for stylistic reasons, but Ifail to see the advantage.
Agreed. Michael Glaesemann grzm seespotcode net
- References:
- Re: BUG #3734: Invalid XML schema output.
- From: Tom Lane
- Re: BUG #3734: Invalid XML schema output.
- From: Harald Armin Massa
- Re: BUG #3734: Invalid XML schema output.
- From: Michael Glaesemann
- Re: BUG #3734: Invalid XML schema output.
- From: Peter Eisentraut
- Re: BUG #3734: Invalid XML schema output.
- Prev by Date: Re: BUG #3734: Invalid XML schema output.
- Next by Date: Re: BUG #3766: tsearch2 index creation error
- Previous by thread: Re: BUG #3734: Invalid XML schema output.
- Next by thread: Re: BUG #3734: Invalid XML schema output.
- Indexes: