- 01 2月, 2007 1 次提交
-
-
由 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".
-
- 16 9月, 2006 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 06 9月, 2006 1 次提交
-
-
由 Tom Lane 提交于
can create or modify rules for the table. Do setRuleCheckAsUser() while loading rules into the relcache, rather than when defining a rule. This ensures that permission checks for tables referenced in a rule are done with respect to the current owner of the rule's table, whereas formerly ALTER TABLE OWNER would fail to update the permission checking for associated rules. Removal of separate RULE privilege is needed to prevent various scenarios in which a grantee of RULE privilege could effectively have any privilege of the table owner. For backwards compatibility, GRANT/REVOKE RULE is still accepted, but it doesn't do anything. Per discussion here: http://archives.postgresql.org/pgsql-hackers/2006-04/msg01138.php
-
- 03 9月, 2006 1 次提交
-
-
由 Tom Lane 提交于
RETURNING play nice with views/rules. To wit, have the rule rewriter rewrite any RETURNING clause found in a rule to produce what the rule's triggering query asked for in its RETURNING clause, in particular drop the RETURNING clause if no RETURNING in the triggering query. This leaves the responsibility for knowing how to produce the view's output columns on the rule author, without requiring any fundamental changes in rule semantics such as adding new rule event types would do. The initial implementation constrains things to ensure that there is exactly one, unconditionally invoked RETURNING clause among the rules for an event --- later we might be able to relax that, but for a post feature freeze fix it seems better to minimize how much invention we do. Per gripe from Jaime Casanova.
-
- 04 1月, 2005 1 次提交
-
-
由 Tom Lane 提交于
-
- 10 3月, 2004 1 次提交
-
-
由 Neil Conway 提交于
the way, fix a typo and make a few SGML cleanups.
-
- 04 3月, 2004 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 30 11月, 2003 1 次提交
-
-
由 PostgreSQL Daemon 提交于
$Header: -> $PostgreSQL Changes ...
-
- 10 9月, 2003 1 次提交
-
-
由 Tom Lane 提交于
discussion. (Still have some work to do editing the remainder.)
-
- 01 9月, 2003 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 22 4月, 2003 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 22 11月, 2002 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 03 9月, 2002 1 次提交
-
-
由 Tom Lane 提交于
more flexible, and improve the error reporting. Also, add documentation for REPLACE RULE/VIEW.
-
- 18 5月, 2002 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 20 4月, 2002 2 次提交
-
-
由 Tom Lane 提交于
_RETURN now, since there's no need to keep 'em unique anymore.
-
由 Tom Lane 提交于
(tgrelid, tgname). This provides an additional check on trigger name uniqueness per-table (which was already enforced by the code anyway). With this change, RelationBuildTriggers will read the triggers in order by tgname, since it's scanning using this index. Since a predictable trigger ordering has been requested for some time, document this behavior as a feature. Also document that rules fire in name order, since yesterday's changes to pg_rewrite indexing cause that too.
-
- 23 3月, 2002 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 10 3月, 2002 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 25 1月, 2002 1 次提交
-
-
由 Tom Lane 提交于
-
- 08 12月, 2001 1 次提交
-
-
由 Thomas G. Lockhart 提交于
between Postgres and PostgreSQL.
-
- 07 11月, 2001 1 次提交
-
-
由 Tom Lane 提交于
-
- 10 10月, 2001 1 次提交
-
-
由 Peter Eisentraut 提交于
output (from pdfjadetex). Also updated instructions to install documentation processing toolchain.
-
- 14 9月, 2001 1 次提交
-
-
由 Tatsuo Ishii 提交于
CREATE RULE bad_rule_combination_1 AS ON SELECT TO emp DO INSTEAD SELECT * FROM toyemp; CREATE RULE bad_rule_combination_2 AS ON SELECT TO toyemp DO INSTEAD SELECT * FROM emp; Tatsuo Ishii
-
- 08 9月, 2001 1 次提交
-
-
由 Tom Lane 提交于
occur unconditionally, even if the rule should otherwise execute conditionally. This is more useful than giving an error, even though it's not truly the correct behavior. Per today's pghackers discussion.
-
- 03 9月, 2001 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 10 7月, 2001 1 次提交
-
-
由 Tom Lane 提交于
in cases of qualified rules as well as unqualified ones. Tweak rules test to avoid cluttering output with dummy SELECT results. Update documentation to match code.
-
- 27 5月, 2001 1 次提交
-
-
由 Peter Eisentraut 提交于
privileges. INSERT and COPY FROM now require INSERT (only). Add privileges regression test.
-
- 14 1月, 2001 1 次提交
-
-
由 Peter Eisentraut 提交于
etc.
-
- 06 1月, 2001 1 次提交
-
-
由 Tom Lane 提交于
what's actually implemented.
-
- 13 12月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
the first paragraph: As an example, say we wish to find all the records that are in the temperature range of other records. In effect, we need to compare the temp_lo and temp_hi attributes of each EMP instance to the temp_lo and temp_hi attributes of all other EMP instances. I believe that EMP should read WEATHER, as the example query that follows joins WEATHER to itself. EMP is often used in Oracle examples. Regards, Graham Other RULE cleanups
-
- 06 10月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
Fix misspelling of disbursion to dispersion.
-
- 22 7月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 21 7月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 20 5月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 13 4月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 08 4月, 2000 4 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 22 7月, 1999 1 次提交
-
-
由 Thomas G. Lockhart 提交于
ecpg reference page still needs formatting.
-