118 Commits (3adc760fb92eab1a8720337a8bf9b66486609eb3)

Author	SHA1	Message	Date
Bruce Momjian	15cb32d93e	This is the final state of the rule system for 6.4 after the ... patch is applied: Rewrite rules on relation level work fine now. Event qualifications on insert/update/delete rules work fine now. I added the new keyword OLD to reference the CURRENT tuple. CURRENT will be removed in 6.5. Update rules can reference NEW and OLD in the rule qualification and the actions. Insert/update/delete rules on views can be established to let them behave like real tables. For insert/update/delete rules multiple actions are supported now. The actions can also be surrounded by parantheses to make psql happy. Multiple actions are required if update to a view requires updates to multiple tables. Regular users are permitted to create/drop rules on tables they have RULE permissions for (DefineQueryRewrite() is now able to get around the access restrictions on pg_rewrite). This enables view creation for regular users too. This required an extra boolean parameter to pg_parse_and_plan() that tells to set skipAcl on all rangetable entries of the resulting queries. There is a new function pg_exec_query_acl_override() that could be used by backend utilities to use this facility. All rule actions (not only views) inherit the permissions of the event relations owner. Sample: User A creates tables T1 and T2, creates rules that log INSERT/UPDATE/DELETE on T1 in T2 (like in the regression tests for rules I created) and grants ALL but RULE on T1 to user B. User B can now fully access T1 and the logging happens in T2. But user B cannot access T2 at all, only the rule actions can. And due to missing RULE permissions on T1, user B cannot disable logging. Rules on the attribute level are disabled (they don't work properly and since regular users are now permitted to create rules I decided to disable them). Rules on select must have exactly one action that is a select (so select rules must be a view definition). UPDATE NEW/OLD rules are disabled (still broken, but triggers can do it). There are two new system views (pg_rule and pg_view) that show the definition of the rules or views so the db admin can see what the users do. They use two new functions pg_get_ruledef() and pg_get_viewdef() that are builtins. The functions pg_get_ruledef() and pg_get_viewdef() could be used to implement rule and view support in pg_dump. PostgreSQL is now the only database system I know, that has rewrite rules on the query level. All others (where I found a rule statement at all) use stored database procedures or the like (triggers as we call them) for active rules (as some call them). Future of the rule system: The now disabled parts of the rule system (attribute level, multiple actions on select and update new stuff) require a complete new rewrite handler from scratch. The old one is too badly wired up. After 6.4 I'll start to work on a new rewrite handler, that fully supports the attribute level rules, multiple actions on select and update new. This will be available for 6.5 so we get full rewrite rule capabilities. Jan	27 years ago
Bruce Momjian	6bd323c6b3	Remove un-needed braces around single statements.	28 years ago
Vadim B. Mikheev	1a105cefbd	Support for subselects. ... ExecReScan for nodeAgg, nodeHash, nodeHashjoin, nodeNestloop and nodeResult. Fixed ExecReScan for nodeMaterial. Get rid of #ifdef INDEXSCAN_PATCH. Get rid of ExecMarkPos and ExecRestrPos in nodeNestloop.	28 years ago
Bruce Momjian	726c3854cb	Inline fastgetattr and others so data access does not use function ... calls.	28 years ago
Bruce Momjian	c60f70b53f	Rename pg_plan and pg_eval to be more meaningful.	28 years ago
Bruce Momjian	4a5b781d71	Break parser functions into smaller files, group together.	28 years ago
Bruce Momjian	3f365ba0fc	Inline memset() as MemSet().	28 years ago
Bruce Momjian	1ea01720d5	heapattr functions now return a Datum, not char *.	28 years ago
Bruce Momjian	59f6a57e59	Used modified version of indent that understands over 100 typedefs.	28 years ago
Bruce Momjian	319dbfa736	Another PGINDENT run that changes variable indenting and case label indenting. Also static variable indenting.	28 years ago
Bruce Momjian	1ccd423235	Massive commit to run PGINDENT on all *.c and *.h files.	28 years ago
Vadim B. Mikheev	0d0254d1fb	SPI manager.	28 years ago
Bruce Momjian	ea5b5357cd	Remove more (void) and fix -Wall warnings.	28 years ago
Vadim B. Mikheev	8e90978146	Fixing bug in INDEXSCAN_PATCH: ... ExecInitIndexScan now works with operands of Param type and (!!!) postquel_execute() now substitutes param values before calling postquel_start().	29 years ago
Marc G. Fournier	ce4c0ce1de	Some compile failure fixes from Keith Parks <emkxp01@mtcc.demon.co.uk>	29 years ago
Marc G. Fournier	87b48ff032	D'Arcy's cleanups	29 years ago
Marc G. Fournier	906651f663	There is a bug in the function executor. The backend crashes while trying to ... execute an sql function containing an utility command (create, notify, ...). The bug is part in the planner, which returns a number of plans different than the number of commands if there are utility commands in the query, and in part in the function executor which assumes that all commands are normal query commands and causes a SIGSEGV trying to execute commands without plan. Submitted by: Massimo Dal Zotto <dz@cs.unitn.it>	29 years ago
Marc G. Fournier	d31084e9d1	Postgres95 1.01 Distribution - Virgin Sources	30 years ago