rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
6,134 Commits 36 Branches 606 Tags 423 MiB
Commit Graph

24 Commits

Author SHA1 Message Date
Jan Wieck e2aef49694 Added empty TOASTER files and corrected some minor glitches 
in regression tests.

Jan
 1999-12-21 00:06:44 +00:00
Tom Lane a8ae19ec3d aggregate(DISTINCT ...) works, per SQL spec. 
Note this forces initdb because of change of Aggref node in stored rules.
 1999-12-13 01:27:21 +00:00
Tom Lane 1891f0e913 Update rules test for extra quoting in rule deparser. 1999-12-06 02:38:56 +00:00
Tom Lane 3eb1c82277 Fix planner and rewriter to follow SQL semantics for tables that are 
mentioned in FROM but not elsewhere in the query: such tables should be
joined over anyway.  Aside from being more standards-compliant, this allows
removal of some very ugly hacks for COUNT(*) processing.  Also, allow
HAVING clause without aggregate functions, since SQL does.  Clean up
CREATE RULE statement-list syntax the same way Bruce just fixed the
main stmtmulti production.
CAUTION: addition of a field to RangeTblEntry nodes breaks stored rules;
you will have to initdb if you have any rules.
 1999-10-07 04:23:24 +00:00
Tom Lane 0655b1500f Less noisy rule display... 1999-10-04 04:38:46 +00:00
Tom Lane b40ac42efb Teach parse_coerce about non-cachable functions (actually, 
make it call eval_const_expressions() so that it doesn't have to know).
 1999-10-02 23:29:19 +00:00
Tom Lane cd243d27ce Revise rule-printing routines to use expandable StringInfo buffers, so that 
they have no hardwired limit on the length of a rule's text.  Fix a couple
of minor bugs in passing --- deparsed UPDATE queries didn't have quotes
around relation name, and quotes and backslashes in constant values weren't
backslash-quoted.
 1999-10-02 01:08:05 +00:00
Tom Lane 9202c4f798 Update rules test expected output to conform to slightly 
more verbose results from ruleutils.c changes.
 1999-08-28 04:00:41 +00:00
Tom Lane b7883d7e3a parse_coerce fix allows early simplification of one 
constant-coercion expression in the rules test.
 1999-08-05 02:35:29 +00:00
Tom Lane f851c6b07d Add another ORDER BY to rules test; got tired of it 'failing' 
every time I tweak the optimizer...
 1999-08-01 04:41:32 +00:00
Tom Lane 2f30d5a34a My recent optimizer changes caused a different plan to 
be picked for one of the complex joins in rules test ... leading to
a different output ordering ...
 1999-07-27 03:53:54 +00:00
Jan Wieck 98981a9f1c Changed "current." into "old." in rule string backparsing 
Jan
 1999-06-02 11:52:29 +00:00
Jan Wieck f4fadbe4db Fixed bug in rules event qualification output. 
Jan
 1999-05-25 08:49:33 +00:00
Jan Wieck fd1647706d Fixed latest regression diff's by omitting viewowner in SELECT from pg_views. 
Jan
 1999-05-17 09:03:26 +00:00
Jan Wieck c8cc45b2f3 Fixed small bug in ruleutils and added output of pg_views and 
pg_rules to rules regression test.

Jan
 1999-05-12 17:59:32 +00:00
Tom Lane dbce02f133 Add ORDER BY clauses to some select-from-view operations 
in rules regression test, in order to eliminate bogus test 'failures'
that occur due to platform-dependent and join-implementation-dependent
ordering of tuples.  I'm not sure that I got all of the SELECTs that need
ordering clauses --- we may need some more.  But this takes care of the
diffs between my platform and Jan's.
 1999-04-15 03:40:50 +00:00
Thomas G. Lockhart dfdb2e5fb0 Remove non-portable queries by replacing getpgusername() with a constant 
string.
 1999-02-23 07:29:19 +00:00
Bruce Momjian e23623584f change pgsql to postgres 1999-02-22 02:06:38 +00:00
Jan Wieck be948af2e8 Added LIMIT/OFFSET functionality including new regression test for it. 
Removed CURRENT keyword for rule queries and changed rules regression
accordingly. CURRENT has beed announced to disappear in v6.5.

Jan
 1999-02-08 14:14:32 +00:00
Jan Wieck 566c712c58 Revert some changes from the INTERSECT/EXPECT patch that broke 
rule system semantics by having Var nodes referenced across multiple
parsetrees when rules split them.

Added more tests to the rules regression test.

The code in question resulted from v6.3 based development and was
a little careless applied to the v6.5 source tree.

Jan
 1999-02-08 01:39:46 +00:00
Jan Wieck 28fc5d7b83 Reenabled parentheses for grouping multiple rule actions and 
added this syntax to rules regression test so it will show up
if someone breaks it again.

Jan
 1999-02-07 19:02:20 +00:00
Tom Lane 1f27facc90 Add ORDER BY to ensure platform-independent results in rules test. 1998-10-28 19:32:43 +00:00
Bruce Momjian f93b6974f9 Here's a combination of all the patches I'm currently waiting 
for against a just updated CVS tree. It contains

        Partial new rewrite system that handles subselects,  view
        aggregate  columns, insert into select from view, updates
        with set col = view-value and select rules restriction to
        view definition.

        Updates  for  rule/view  backparsing utility functions to
        handle subselects correct.


        New system views pg_tables and pg_indexes (where you  can
        see the complete index definition in the latter one).

        Enabling array references on query parameters.

        Bugfix for functional index.

        Little changes to system views pg_rules and pg_views.


    The rule system isn't a release-stopper any longer.

    But  another  stopper  is  that  I  don't  know if the latest
    changes to PL/pgSQL (not already in CVS) made it  compile  on
    AIX. Still wait for some response from Dave.

Jan
 1998-10-02 16:28:04 +00:00
Thomas G. Lockhart 5a68fd56cd Consolidate Jan's rules test into one file. 
Remove dependency on a specific Postgres user name in the results
 (Check result against CURRENT_USER with a boolean instead).
 1998-09-16 14:35:37 +00:00