postgres

Commit Graph

Author	SHA1	Message	Date
Bruce Momjian	07842084fe	pgindent run over code.	27 years ago
Bruce Momjian	1a87c14c9c	I am sorry, I misinterpreted the still failing trigger regression test. The offending code has been removed, the action is now always dependent :-) I suggest the following patch, to finally make trigger regression happy again: <<refint1.patch>> After that you can remove the following from TODO: Remove ERROR: check_primary_key: even number of arguments should be specified Trigger regression test fails Andreas	27 years ago
Bruce Momjian	d489fdfc7f	I send you a attach of my modified refint.c that works with a new policy in cascade mode . Please Read README.MAX . I do not know if you are the author of refint.c , but if not please tell me who is . Thank you ( excuse me for my bad english) . Massimo Lambertini massimo.lambertini@everex.it	27 years ago
Bruce Momjian	98ad3fcfaf	Hi All, I've changed the check_primary_key() function code to allow for either the "automatic insert key rule" or "dependent insert key rule". Previously it restricted the addtion of a child entry if the corresponding parent entry was not there. Now if the option is "automatic" it will add an entry in the parent too ( it will be successful if there are no no-null fields in the parent apart from the primary key). The way to use it now is: :/* * check_primary_key () -- check that key in tuple being inserted/updated * references existing tuple in "primary" table. * Though it's called without args You have to specify referenced * table/keys while creating trigger: key field names in triggered table, * referenced table name, referenced key field names,type of action [automatic\|dependent]: * EXECUTE PROCEDURE * check_primary_key ('Fkey1', 'Fkey2', 'Ptable', 'Pkey1', 'Pkey2', '[automatic\|dependent]'). */ I am attaching the new ../contrib/spi/refint.c file which will do this. I will be glad to help in case of any problems. - Anand.	27 years ago
Bruce Momjian	3abf496b8e	> > There is a bug in check_foreign_key of refint.c which is bundled with > > the standard distribution. It occurs when a trigger calling this > > function recursively fires another trigger which calls the same > > function. The calling check_foreign_key loses its plan informantion and > > when it tries to use it the backend closes its channel. You can check it > > with the sql script I am attaching below. > > The solution to this is to do a find_plan again before executing it at > > line 483 of refint.c. > > Therefore two more lines should be added before line 483: Anand Surelia	27 years ago
Bruce Momjian	a32450a585	pgindent run before 6.3 release, with Thomas' requested changes.	28 years ago
Marc G. Fournier	b59e20db1a	From: plh@opim.uconn.edu Missing = in an update	28 years ago
Bruce Momjian	9d00fbbeb0	Change some labels in bootparse to make ctags happy. Clean up outfunc/readfunc code and add missing fields for Query structure and new Union fields. Fix optimizer bug shown in new \do command. Change WARN to ERROR in contrib and regression stuff.	28 years ago
Vadim B. Mikheev	7f97e05b09	char* --> Datum	28 years ago
Vadim B. Mikheev	b6f348cd33	General trigger functions for referential integrity.	28 years ago

10 Commits (d35eebe748a652f53bfa4fcce7768b964942bb7f)