user/sven/postgresql.git

Age	Commit message (Collapse)	Author
2008-03-28	Support statement-level ON TRUNCATE triggers. Simon Riggs	Tom Lane

2007-02-01	Consistenly use colons before '<programlisting>' blocks, where	Bruce Momjian
	appropriate.
2007-01-31	Update documentation on may/can/might:	Bruce Momjian
	Standard English uses "may", "can", and "might" in different ways: may - permission, "You may borrow my rake." can - ability, "I can lift that log." might - possibility, "It might rain today." Unfortunately, in conversational English, their use is often mixed, as in, "You may use this variable to do X", when in fact, "can" is a better choice. Similarly, "It may crash" is better stated, "It might crash". Also update two error messages mentioned in the documenation to match.
2006-10-23	Spellchecking and such	Peter Eisentraut

2006-10-21	Editorial improvements for recent plpython doc updates.	Tom Lane

2006-10-16	Remove use of '<' and '>' in SGML, use '&' escapes.	Bruce Momjian
	Update find_gt_lt to allow grep parameters to be passed into it.
2006-09-03	Remove duplicated index entry.	Tom Lane

2006-09-03	Fix broken markup.	Tom Lane

2006-09-02	Allow PL/python to return composite types and result sets	Bruce Momjian
	Sven Suursoho
2006-05-26	Add table_name and table_schema to plpython trigger data, plus docs and ↵	Andrew Dunstan
	regression test.
2005-05-20	Add some links to the CREATE FUNCTION reference page when describing	Neil Conway
	function definition for particular PLs. Original patch from David Fetter, editorializing by Neil Conway.
2005-04-09	We don't put URL's in ulink's because the URL is always generated, but	Bruce Momjian
	we can put words in ulink and the URL will still be printed. per Peter
2005-03-31	Adjust SGML ulink tags to the URL is always displayed in our printed docs.	Bruce Momjian

2004-12-30	More minor updates and copy-editing.	Tom Lane

2004-12-17	Hook up the plpython result-object nrows and status methods correctly.	Tom Lane
	Adjust documentation to match current reality.
2004-09-13	Redesign query-snapshot timing so that volatile functions in READ COMMITTED	Tom Lane
	mode see a fresh snapshot for each command in the function, rather than using the latest interactive command's snapshot. Also, suppress fresh snapshots as well as CommandCounterIncrement inside STABLE and IMMUTABLE functions, instead using the snapshot taken for the most closely nested regular query. (This behavior is only sane for read-only functions, so the patch also enforces that such functions contain only SELECT commands.) As per my proposal of 6-Sep-2004; I note that I floated essentially the same proposal on 19-Jun-2002, but that discussion tailed off without any action. Since 8.0 seems like the right place to be taking possibly nontrivial backwards compatibility hits, let's get it done now.
2004-05-16	Add documentation for the new "dollar quoting" feature, and update existing	Neil Conway
	examples to use dollar quoting when appropriate. Original patch from David Fetter, additional work and editorializing by Neil Conway.
2003-11-29	$Header: -> $PostgreSQL Changes ...	PostgreSQL Daemon

2003-11-12	Documentation cleanup	Peter Eisentraut

2003-09-12	Update obsolete examples of error messages; various other minor editing.	Tom Lane

2003-08-31	Add/edit index entries.	Peter Eisentraut

2003-07-01	Fix documentation comment about restricted environments, per Kevin Jacobs.	Tom Lane

2003-06-30	Rename plpython to plpythonu, and update documentation to reflect its	Tom Lane
	now-untrusted status.
2003-04-07	General editing	Peter Eisentraut

2002-10-21	Small update for the removal of some memory leaks in plpython SGML example.	Bruce Momjian
	Nigel J. Andrews
2002-09-23	The valid return value should be MODIFY instead of MODIFIED.	Bruce Momjian
	The error message said so :-) In 25.3. Using PL/Python If the trigger "when" is BEFORE, you may return None or "OK" from the Python function to indicate the tuple is unmodified, "SKIP" to abort the event, or "MODIFIED" to indicate you've modified the tuple. should read If the trigger "when" is BEFORE, you may return None or "OK" from the Python function to indicate the tuple is unmodified, "SKIP" to abort the event, or "MODIFY" to indicate you've modified the tuple. elein
2002-09-22	Fix busted markup.	Tom Lane

2002-09-21	Add more appropriate markup.	Peter Eisentraut

2002-09-18	Update installation instructions and put mostly everything in one place.	Peter Eisentraut
	Also, some editing in PL/Perl and PL/Python chapters.
2002-03-22	Spell checking and markup additions	Peter Eisentraut

2002-03-06	Update docs for new stored procedure error levels.	Bruce Momjian

2002-01-07	Editorial review	Peter Eisentraut

2001-11-21	Deprecate 'current' for date/time input.	Thomas G. Lockhart
	Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
2001-11-20	Added a few paragraphs to explain current restricted execution environment,	Bruce Momjian
	and error handling behavior. Bradley McLean
2001-11-12	Add some more index entries.	Peter Eisentraut

2001-09-13	Replace ASCII-quotes with proper markup.	Peter Eisentraut

2001-09-12	Here's some matching documentation, including some other	Bruce Momjian
	undocumented items in TD. Should doc patches alse be sent to pgsql-patches, or do I have to subscribe to pgsql-docs? The archive link for pgsql-patches is broken, and I don't see any patches in spot checking the archive for pgsql-docs. -Brad McLean.
2001-09-10	Markup and spell-check run over Programmer's Guide (rather incomplete still).	Peter Eisentraut

2001-05-12	PL/Python should build portably now, if you can get over the fact that	Peter Eisentraut
	there's no shared libpython. Test suite works as well. Also, add some documentation.