postgres

Commit Graph

Author	SHA1	Message	Date
Bruce Momjian	6ad4249b5c	Add more 9.0 release note documentation links.	16 years ago
Peter Eisentraut	a401226bd8	Prevent the injection of invalidly encoded strings by PL/Python into PostgreSQL with a few strategically placed pg_verifymbstr calls.	16 years ago
Peter Eisentraut	66cac8feab	Add some more structure and bits of information to PL/Python documentation	16 years ago
Peter Eisentraut	adb7764030	PL/Python DO handler Also cleaned up some redundancies between the primary error messages and the error context in PL/Python. Hannu Valtonen	16 years ago
Peter Eisentraut	8f649c9ac4	Add documentation why reassigning PL/Python function parameters in the function body can have undesirable outcomes. (bug #5232)	16 years ago
Peter Eisentraut	dd4cd55c15	Python 3 support in PL/Python Behaves more or less unchanged compared to Python 2, but the new language variant is called plpython3u. Documentation describing the naming scheme is included.	16 years ago
Peter Eisentraut	db7386187f	PL/Python array support Support arrays as parameters and return values of PL/Python functions.	16 years ago
Alvaro Herrera	3fe3b81183	Update URL to Python bug tracker. Backpatch to 8.3; doesn't seem worthy of further backpatch.	17 years ago
Tom Lane	7692d8d5b7	Support statement-level ON TRUNCATE triggers. Simon Riggs	18 years ago
Bruce Momjian	09a9f10e7f	Consistenly use colons before '<programlisting>' blocks, where appropriate.	19 years ago
Bruce Momjian	a134ee3379	Update documentation on may/can/might: 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.	19 years ago
Peter Eisentraut	0f763503ff	Spellchecking and such	19 years ago
Tom Lane	425417d498	Editorial improvements for recent plpython doc updates.	19 years ago
Bruce Momjian	389fad1e6b	Remove use of '<' and '>' in SGML, use '&' escapes. Update find_gt_lt to allow grep parameters to be passed into it.	19 years ago
Tom Lane	676d1b4e67	Remove duplicated index entry.	20 years ago
Tom Lane	4ae15f29f7	Fix broken markup.	20 years ago
Bruce Momjian	819f22a302	Allow PL/python to return composite types and result sets Sven Suursoho	20 years ago
Andrew Dunstan	0a269db9cf	Add table_name and table_schema to plpython trigger data, plus docs and regression test.	20 years ago
Neil Conway	4de23092d0	Add some links to the CREATE FUNCTION reference page when describing function definition for particular PLs. Original patch from David Fetter, editorializing by Neil Conway.	21 years ago
Bruce Momjian	0e2f88a6d5	We don't put URL's in ulink's because the URL is always generated, but we can put words in ulink and the URL will still be printed. per Peter	21 years ago
Bruce Momjian	fd977434b3	Adjust SGML ulink tags to the URL is always displayed in our printed docs.	21 years ago
Tom Lane	883ac5ca7a	More minor updates and copy-editing.	21 years ago
Tom Lane	dfdae5d63c	Hook up the plpython result-object nrows and status methods correctly. Adjust documentation to match current reality.	21 years ago
Tom Lane	b2c4071299	Redesign query-snapshot timing so that volatile functions in READ COMMITTED 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.	22 years ago
Neil Conway	8295c27c89	Add documentation for the new "dollar quoting" feature, and update existing examples to use dollar quoting when appropriate. Original patch from David Fetter, additional work and editorializing by Neil Conway.	22 years ago
PostgreSQL Daemon	969685ad44	$Header: -> $PostgreSQL Changes ...	22 years ago
Peter Eisentraut	934c21344c	Documentation cleanup	22 years ago
Tom Lane	6e59122490	Update obsolete examples of error messages; various other minor editing.	23 years ago
Peter Eisentraut	c326d8f4f2	Add/edit index entries.	23 years ago
Tom Lane	dc8dec6a70	Fix documentation comment about restricted environments, per Kevin Jacobs.	23 years ago
Tom Lane	6115224448	Rename plpython to plpythonu, and update documentation to reflect its now-untrusted status.	23 years ago
Peter Eisentraut	a8cb3368db	General editing	23 years ago
Bruce Momjian	b6f0c50232	Small update for the removal of some memory leaks in plpython SGML example. Nigel J. Andrews	24 years ago
Bruce Momjian	909a8377db	The valid return value should be MODIFY instead of MODIFIED. 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	24 years ago
Tom Lane	634e440b58	Fix busted markup.	24 years ago
Peter Eisentraut	bc49968764	Add more appropriate markup.	24 years ago
Peter Eisentraut	da123b7c58	Update installation instructions and put mostly everything in one place. Also, some editing in PL/Perl and PL/Python chapters.	24 years ago
Peter Eisentraut	b6ea172ace	Spell checking and markup additions	24 years ago
Bruce Momjian	ade0fe5cb4	Update docs for new stored procedure error levels.	24 years ago
Peter Eisentraut	731204e090	Editorial review	24 years ago
Thomas G. Lockhart	2475e87481	Deprecate 'current' for date/time input. Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.	24 years ago
Bruce Momjian	05979312ed	Added a few paragraphs to explain current restricted execution environment, and error handling behavior. Bradley McLean	24 years ago
Peter Eisentraut	3c879e3738	Add some more index entries.	24 years ago
Peter Eisentraut	351a0c1736	Replace ASCII-quotes with proper markup.	25 years ago
Bruce Momjian	33a82e7fd8	Here's some matching documentation, including some other 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.	25 years ago
Peter Eisentraut	a457d33516	Markup and spell-check run over Programmer's Guide (rather incomplete still).	25 years ago
Peter Eisentraut	bbc3920fe9	PL/Python should build portably now, if you can get over the fact that there's no shared libpython. Test suite works as well. Also, add some documentation.	25 years ago

47 Commits (de66effede5f7cb6da258e1bfe6fc508ad4cf940)