11 Commits (0a97cb37fc29dac05fd5aa13df91ba8431faea23)

Author	SHA1	Message	Date
Bruce Momjian	cfd2728100	This patch makes a minor cleanup to the implementation of PERFORM in ... PL/PgSQL. Previously, it had been bundled together with the assign statement implementation, for some reason that wasn't clear to me (they certainly don't share any code with one another). So I separated them and made PERFORM a statement like any other. No changes in functionality. Along the way, I added some regression tests for PERFORM, added a bunch more SGML tags to the PL/PgSQL docs, and removed an obsolete comment relating to the implementation of RETURN NEXT. Neil Conway	23 years ago
Tom Lane	470a1048ec	plpgsql functions can return RECORD, per Neil Conway.	24 years ago
Tom Lane	e107f3a7e3	PL/pgSQL functions can return sets. Neil Conway's patch, modified so ... that the functionality is available to anyone via ReturnSetInfo, rather than hard-wiring it to PL/pgSQL.	24 years ago
Tom Lane	40faa4a590	Transpose info from src/pl/plpgsql/test/README into standard regression test file.	24 years ago
Tom Lane	b663f3443b	Add a bunch of pseudo-types to replace the behavior formerly associated ... with OPAQUE, as per recent pghackers discussion. I still want to do some more work on the 'cstring' pseudo-type, but I'm going to commit the bulk of the changes now before the tree starts shifting under me ...	24 years ago
Bruce Momjian	ebe1be1321	This patch improves the behavior of FOUND in PL/PgSQL. In Oracle, ... FOUND is set whenever a SELECT INTO returns > 0 rows, *or* when an INSERT, UPDATE, or DELETE affects > 0 rows. We implemented the first part of this behavior, but not the second. I also improved the documentation on the various situations in which FOUND can be set (excluding inside FOR loops, which I still need to think about), and added some regression tests for this behavior. Neil Conway	24 years ago
Tom Lane	ae3129fd03	Quick-and-dirty fix for recursive plpgsql functions, per bug report from ... Frank Miles 7-Sep-01. This is really just sticking a finger in the dike. Frank's case works now, but we still couldn't support a recursive function returning a set. Really need to restructure querytrees and execution state so that the querytree is *read only*. We've run into this over and over and over again ... it has to happen sometime soon.	25 years ago
Tom Lane	9ace03183c	Some small polishing of Mark Hollomon's cleanup of DROP command: might ... as well allow DROP multiple INDEX, RULE, TYPE as well. Add missing CommandCounterIncrement to DROP loop, which could cause trouble otherwise with multiple DROP of items affecting same catalog entries. Try to bring a little consistency to various error messages using 'does not exist', 'nonexistent', etc --- I standardized on 'does not exist' since that's what the vast majority of the existing uses seem to be.	26 years ago
Tom Lane	fc0a46dc16	Remove CVS $Header lines from a couple of regress test files that had ... them --- it is just *way* too painful to keep expected results in sync when these are present.	26 years ago
Thomas G. Lockhart	d1e6368816	Clean up header for uniform appearance throughout tests.	26 years ago
Marc G. Fournier	2074b5f1ad	failed to add some of Jan's files :(	28 years ago
Bruce Momjian	28d90a5f8b	move plpgsql	28 years ago
Bruce Momjian	0c5e541a9a	move plpgsql to src/pl for Jan.	28 years ago
Bruce Momjian	863a62064c	As proposed, here is the current version of PL/pgSQL. The ... test isn't that complete up to now, but I think it shows enough of the capabilities of the module. The Makefile assumes it is located in a directory under pgsql/src/pl. Since it includes Makefile.global and Makefile.port and doesn't use any own compiler/linker calls, it should build on most of our supported platforms (I only tested under Linux up to now). It requires flex and bison I think. Maybe we should ship prepared gram.c etc. like for the main parser too? Jan	28 years ago