[BUGS] BUG #3776: problem with drop database or dropdb
The following bug has been logged online: Bug reference: 3776 Logged by: ludo Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1 Operating system: windows 2003 Description:problem with drop database or dropdb Details: Hello. When i do dropdb.exe database_name or drop database database_name, nothing happen and postgresql doesn't work anymore. I have to kill postgresql process and to stop postgresql service. ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [BUGS] BUG #3734: Invalid XML schema output.
> > I assumed XML is for both human and program reading; in fact, I thought > that was its big benefit. I assume we are taking the difference between > "" vs "", right? I will admit I don't know much about XML. > > within XHTML it is recommended to use , because some parsers will not parse it correctly without that space. I guess some pure XML-Parsers may have the same problem (and be it only the IE-XML-Parser) Harald -- GHUM Harald Massa persuadere et programmare Harald Armin Massa Spielberger Straße 49 70435 Stuttgart 0173/9409607 fx 01212-5-13695179 - EuroPython 2008 will take place in Vilnius, Lithuania - Stay tuned!
Re: [BUGS] BUG #3734: Invalid XML schema output.
Tom Lane wrote: > Euler Taveira de Oliveira <[EMAIL PROTECTED]> writes: > > Bruce Momjian wrote: > >>> Agreed. Feel free to add whitespace before every /> of simple xml > >>> elements. > >> > >> Uh, was this done? > >> > > Nope. Attached is a patch that does it. > > Er ... why exactly is it a good idea to bloat XML output with cosmetic > whitespace? I should think that only programs, not humans, read XML for > the most part. I assumed XML is for both human and program reading; in fact, I thought that was its big benefit. I assume we are taking the difference between "" vs "", right? I will admit I don't know much about XML. -- Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [BUGS] BUG #3734: Invalid XML schema output.
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 correctly Yes, 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 I fail to see the advantage. Agreed. Michael Glaesemann grzm seespotcode net ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [BUGS] BUG #3734: Invalid XML schema output.
On Nov 23, 2007, at 11:22 , Harald Armin Massa wrote: within XHTML it is recommended to use , because some parsers will not parse it correctly without that space. It's because some browser *HTML* parsers that aren't fully XML compliant won't parse it correctly, not because some XML parsers have a problem with it. Any XML parser worthy of the name should have no problem with (or any other self-closing empty element tag, for that matter). Michael Glaesemann grzm seespotcode net ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [BUGS] BUG #3734: Invalid XML schema output.
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 correctly Yes, 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 I fail to see the advantage. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
