Re: [DOCS] Table A-1. PostgreSQL Error Codes (WITH constants)

> What exactly is the point of the change at all? Take a typical line in the table: Error Code | Meaning 23502 | NOT NULL VIOLATION Now assume I want to catch this exception in a plpgsql function: CREATE OR REPLACE FUNCTION foo() /* boilerplate omitted */ EXCEPTION WHEN NOT_NULL_VIOLA

Re: [DOCS] [PATCHES] pl/pgSQL doco patch

d Tom, I think that would lend weight to allowing PostgreSQL to do it too (not because it's The Right Thing, but for interoperability and ease of porting). Thoughts? Regards, Philip. -- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code

[DOCS] pl/pgSQL doco patch

Hi, I supplied a minor doco patch relating to porting pl/SQL to pl/pgSQL: http://archives.postgresql.org/pgsql-hackers/2005-10/msg01295.php. Also attached here. Could someone please review and apply this for me? Regards, Philip. -- "Debugging is twice as hard as writing the code i

Re: [DOCS] Online comments system

Thanks for the pointers - I'll talk to pgsql-www if I have any more questions. Yours, Philip pgpq76i1HiYSJ.pgp Description: PGP signature

[DOCS] Online comments system

echnical side of the system? Is the source code available? Thanks in advance, Philip ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings

Re: [DOCS] Suggested patch to plpgsql docs (7.4beta)

t; too. > > I figured everyone would assume that. I know of no language that will > execute a loop listed as 10 ... 1. Basic on my first computer suppported it, though the syntax was FOR $i in 10 TO 1 STEP -1 PRINT $i NEXT I think it is worth stating explicitly