[DOCS] truth table missing values

2003-08-04 Thread Dennis Björklund
The truth table in http://www.postgresql.org/docs/7.3/static/functions.html#FUNCTIONS-LOGICAL is missing some rows. The meaning is clear if you know that AND and OR is commutative but that is not written there either. The reason I found this at all is because in mysql AND is not commutative. I

[DOCS] Incorrect REVOKE command in docs

2003-08-04 Thread Stephen Frost
Greetings, The 'REVOKE' command given in section 2.8.4 under Chapter 2. "Data Definition" is not correct. The command should be: REVOKE CREATE ON SCHEMA public FROM PUBLIC; Note that 'SCHEMA' is missing. This is at least on the web page: http://www.postgresql.org/docs/7.3/static/ddl-

Re: [DOCS] Incorrect REVOKE command in docs

2003-08-04 Thread Peter Eisentraut
Already fixed in 7.4. Thanks. Stephen Frost writes: > Greetings, > > The 'REVOKE' command given in section 2.8.4 under Chapter 2. "Data > Definition" is not correct. The command should be: > > REVOKE CREATE ON SCHEMA public FROM PUBLIC; > > Note that 'SCHEMA' is missing. This is at lea

Re: [DOCS] truth table missing values

2003-08-04 Thread Peter Eisentraut
Dennis Björklund writes: > The truth table in > > http://www.postgresql.org/docs/7.3/static/functions.html#FUNCTIONS-LOGICAL > > is missing some rows. The meaning is clear if you know that AND and OR is > commutative but that is not written there either. I've added a note that they are commutativ

Re: [DOCS] Mysql -> Postgresql pitfalls

2003-08-04 Thread scott.marlowe
On Fri, 1 Aug 2003, Chad N. Tindel wrote: > > > Excellent! That is exactly what I'm talking about. > > > > > > BTW, the "my2pg.pl" link is a dead link. > > > > This is probably something that could be codified a bit here in the news > > group. > > > > I'd say the pitfalls I'm aware of are: >

Re: [DOCS] Mysql -> Postgresql pitfalls

2003-08-04 Thread scott.marlowe
On Sat, 2 Aug 2003, Chad N. Tindel wrote: > > > As a programmer, I personally would never write code that kept > > > people from running things as root. I mean, what is the point? > > > > If someone roots your box, it's not our fault. Simple as that. > > I didn't say "require them to run as a

Re: [DOCS] truth table missing values

2003-08-04 Thread scott.marlowe
On Mon, 4 Aug 2003, Dennis Björklund wrote: > The reason stated in > http://www.mysql.com/documentation/mysql/bychapter/manual_Introduction.html#Differences_from_ANSI > > is > > "NULL AND FALSE will evaluate to NULL and not to FALSE. This is because we > don't think it's good to have to evaluat

Re: [DOCS] Mysql -> Postgresql pitfalls

2003-08-04 Thread Josh Berkus
Folks, Are we actually arguing about whether or not Postmaster should be allowed to run as root? I thought this question was settled, like, 5 years ago. If migrating MySQL users have trouble with it, maybe we should focus on supplying a battery of sample startup and maintainence scripts for

Re: [DOCS] Mysql -> Postgresql pitfalls

2003-08-04 Thread Josh Berkus
Chad, Scott: > > Yes. The documentation very clearly states using sequences instead of > > auto-increment, but it doesn't make it clear that inserting the id's into > > data by hand doesn't cause the sequence to be auto-matically incremented. > > It'd be nice of postgres had a way to trigger an

Re: [DOCS] Mysql -> Postgresql pitfalls

2003-08-04 Thread scott.marlowe
On Mon, 4 Aug 2003, Josh Berkus wrote: > Folks, > > Are we actually arguing about whether or not Postmaster should be allowed to > run as root? > > I thought this question was settled, like, 5 years ago. > > If migrating MySQL users have trouble with it, maybe we should focus on > supplyin

Re: [DOCS] Mysql -> Postgresql pitfalls

2003-08-04 Thread Lamar Owen
On Saturday 02 August 2003 13:04, Chad N. Tindel wrote: > I didn't say "require them to run as a non-root user". I said "Give them > the choice to decide what is correct for their environment". In the case > of apache, there are many internal webservers that are not exposed to the > threat of the

Re: [DOCS] Mysql -> Postgresql pitfalls

2003-08-04 Thread scott.marlowe
On Mon, 4 Aug 2003, Chad N. Tindel wrote: > > > > Yes. The documentation very clearly states using sequences instead of > > > > auto-increment, but it doesn't make it clear that inserting the id's into > > > > data by hand doesn't cause the sequence to be auto-matically incremented. > > > > It'd

Re: [DOCS] Mysql -> Postgresql pitfalls

2003-08-04 Thread scott.marlowe
On Mon, 4 Aug 2003, Chad N. Tindel wrote: > > > > FWIW, in 7.5 we're likely to implement SQL3 IDENTITY columns ... basically > > > > just a SERIAL column where you don't have the option of inserting your own > > > > value, you have to take what it gives you. > > > > > > Interesting... how do yo

Re: [DOCS] Mysql -> Postgresql pitfalls

2003-08-04 Thread Chad N. Tindel
> Are we actually arguing about whether or not Postmaster should be allowed to > run as root? > > I thought this question was settled, like, 5 years ago. I don't think my responses have been being posted to the list... they're probably all blocked pending approval of some administrator. No,

Re: [DOCS] Mysql -> Postgresql pitfalls

2003-08-04 Thread Chad N. Tindel
> > I didn't say "require them to run as a non-root user". I said "Give them > > the choice to decide what is correct for their environment". In the case > > of apache, there are many internal webservers that are not exposed to the > > threat of the public internet; for such servers, it may be ap

Re: [DOCS] Mysql -> Postgresql pitfalls

2003-08-04 Thread Chad N. Tindel
> > > Yes. The documentation very clearly states using sequences instead of > > > auto-increment, but it doesn't make it clear that inserting the id's into > > > data by hand doesn't cause the sequence to be auto-matically incremented. > > > It'd be nice of postgres had a way to trigger an update

Re: [DOCS] Mysql -> Postgresql pitfalls

2003-08-04 Thread Chad N. Tindel
> > > FWIW, in 7.5 we're likely to implement SQL3 IDENTITY columns ... basically > > > just a SERIAL column where you don't have the option of inserting your own > > > value, you have to take what it gives you. > > > > Interesting... how do you import data from a dump with such columsn? > > Eas

Re: [DOCS] Mysql -> Postgresql pitfalls

2003-08-04 Thread Rod Taylor
> speak in the \copy command. I.e. you wouldn't use inserts to load your > data, you'd use a bulk copy, which bypassess all the serial / IDENTITY > stuff. Basically, with the IDENTITY type, if you try to insert a value, COPY enforces everything that insert does. It's simply a little quicker

Re: [DOCS] Mysql -> Postgresql pitfalls

2003-08-04 Thread Lamar Owen
On Monday 04 August 2003 13:54, Chad N. Tindel wrote: > True. There are good reasons to not run apache as root. There are also > perfectly valid reasons to run it as root, for such users who want to make > an informed decision. Name one. > My posts to the list are not going through. I am NOT a

[DOCS] man pages for v7.4 ... ?

2003-08-04 Thread Marc G. Fournier
Peter, I have the following man pages being copied in in my mk-beta script: %ls -ld /var/spool/ftp/pub/dev/doc/man.tar.gz -rw-r--r-- 1 petere wheel 146009 Nov 21 2002 /var/spool/ftp/pub/dev/doc/man.tar.gz Appears a bit old ... ? :) Just checked the mk-snapshot script, and its copying in the

[DOCS] duplicated index entry found ...

2003-08-04 Thread The Hermit Hacker
Non-critical, but figured I'd mention it ... this was from the beta build this evening ... /usr/local/bin/perl /usr/local/share/sgml/docbook/dsssl/modular/bin/collateindex.pl -f -g -i 'bookindex' -o bookindex.sgml HTML.index Processing HTML.index... 568 entries loaded... duplicated index entry f