1. 05 Apr, 2002 1 commit
  2. 02 Apr, 2002 1 commit
  3. 29 Mar, 2002 1 commit
  4. 22 Mar, 2002 1 commit
    • Tom Lane's avatar
      A little further progress on schemas: push down RangeVars into · 108a0ec8
      Tom Lane authored
      addRangeTableEntry calls.  Remove relname field from RTEs, since
      it will no longer be a useful unique identifier of relations;
      we want to encourage people to rely on the relation OID instead.
      Further work on dumping qual expressions in EXPLAIN, too.
      108a0ec8
  5. 21 Mar, 2002 1 commit
    • Tom Lane's avatar
      First phase of SCHEMA changes, concentrating on fixing the grammar and · 95ef6a34
      Tom Lane authored
      the parsetree representation.  As yet we don't *do* anything with schema
      names, just drop 'em on the floor; but you can enter schema-compatible
      command syntax, and there's even a primitive CREATE SCHEMA command.
      No doc updates yet, except to note that you can now extract a field
      from a function-returning-row's result with (foo(...)).fieldname.
      95ef6a34
  6. 12 Mar, 2002 1 commit
    • Tom Lane's avatar
      Restructure representation of join alias variables. An explicit JOIN · 6eeb95f0
      Tom Lane authored
      now has an RTE of its own, and references to its outputs now are Vars
      referencing the JOIN RTE, rather than CASE-expressions.  This allows
      reverse-listing in ruleutils.c to use the correct alias easily, rather
      than painfully reverse-engineering the alias namespace as it used to do.
      Also, nested FULL JOINs work correctly, because the result of the inner
      joins are simple Vars that the planner can cope with.  This fixes a bug
      reported a couple times now, notably by Tatsuo on 18-Nov-01.  The alias
      Vars are expanded into COALESCE expressions where needed at the very end
      of planning, rather than during parsing.
      Also, beginnings of support for showing plan qualifier expressions in
      EXPLAIN.  There are probably still cases that need work.
      initdb forced due to change of stored-rule representation.
      6eeb95f0
  7. 05 Nov, 2001 1 commit
  8. 25 Oct, 2001 1 commit
  9. 08 Oct, 2001 1 commit
  10. 28 Sep, 2001 1 commit
    • Thomas G. Lockhart's avatar
      Measure the current transaction time to milliseconds. · 6f58115d
      Thomas G. Lockhart authored
      Define a new function, GetCurrentTransactionStartTimeUsec() to get the time
       to this precision.
      Allow now() and timestamp 'now' to use this higher precision result so
       we now have fractional seconds in this "constant".
      Add timestamp without time zone type.
      Move previous timestamp type to timestamp with time zone.
      Accept another ISO variant for date/time values: yyyy-mm-ddThh:mm:ss
       (note the "T" separating the day from hours information).
      Remove 'current' from date/time types; convert to 'now' in input.
      Separate time and timetz regression tests.
      Separate timestamp and timestamptz regression test.
      6f58115d
  11. 17 Sep, 2001 1 commit
  12. 10 Sep, 2001 1 commit
    • Bruce Momjian's avatar
      Bug #1: attribute name when column is type cast: · d70a944e
      Bruce Momjian authored
      Given the following table:
      
      test=# \d f
                Table "f"
       Column |  Type   | Modifiers
      --------+---------+-----------
       i      | integer |
       test   | text    |
      
      If I do the following:
      
      test=# insert into f values(1,'test');
      INSERT 139549 1
      test=# select i::int8,test from f;
       ?column? | test
      ----------+------
              1 | test
      (1 row)
      
      It doesn't make much sense that the first column should be called
      '?column?'.
      
      The patch results in the output appearing like this:
      
      test=# select i::int8,test from f;
       i | test
      ---+------
       1 | test
      (1 row)
      
      ----------
      
      Gavin Sherry
      d70a944e
  13. 09 Aug, 2001 1 commit
  14. 24 Jun, 2001 1 commit
  15. 23 Jun, 2001 1 commit
    • Bruce Momjian's avatar
      > Marko Kreen <marko@l-t.ee> writes: · 6a7f23c2
      Bruce Momjian authored
      > > secure_ctx changes too.  it will be PGC_BACKEND after '-p'.
      >
      > Oh, okay, I missed that part.  Could we see the total state of the
      > patch --- ie, a diff against current CVS, not a bunch of deltas?
      > I've gotten confused about what's in and what's out.
      
      Ok, here it is.  Cleared the ctx comment too - after -p
      it will be PGC_BACKEND in any case.
      
      Marko Kreen
      6a7f23c2
  16. 21 May, 2001 1 commit
  17. 22 Mar, 2001 1 commit
  18. 14 Feb, 2001 1 commit
    • Tom Lane's avatar
      Change scoping of table and join refnames to conform to SQL92: a JOIN · 4a66f9dd
      Tom Lane authored
      clause with an alias is a <subquery> and therefore hides table references
      appearing within it, according to the spec.  This is the same as the
      preliminary patch I posted to pgsql-patches yesterday, plus some really
      grotty code in ruleutils.c to reverse-list a query tree with the correct
      alias name depending on context.  I'd rather not have done that, but unless
      we want to force another initdb for 7.1, there's no other way for now.
      4a66f9dd
  19. 24 Jan, 2001 1 commit
  20. 29 Sep, 2000 1 commit
    • Tom Lane's avatar
      Subselects in FROM clause, per ISO syntax: FROM (SELECT ...) [AS] alias. · 3a94e789
      Tom Lane authored
      (Don't forget that an alias is required.)  Views reimplemented as expanding
      to subselect-in-FROM.  Grouping, aggregates, DISTINCT in views actually
      work now (he says optimistically).  No UNION support in subselects/views
      yet, but I have some ideas about that.  Rule-related permissions checking
      moved out of rewriter and into executor.
      INITDB REQUIRED!
      3a94e789
  21. 12 Sep, 2000 1 commit
  22. 08 Aug, 2000 1 commit
    • Tom Lane's avatar
      Remove 'func_tlist' from Func expression nodes, likewise 'param_tlist' · 62e29fe2
      Tom Lane authored
      from Param nodes, per discussion a few days ago on pghackers.  Add new
      expression node type FieldSelect that implements the functionality where
      it's actually needed.  Clean up some other unused fields in Func nodes
      as well.
      NOTE: initdb forced due to change in stored expression trees for rules.
      62e29fe2
  23. 15 Jun, 2000 1 commit
  24. 30 May, 2000 1 commit
  25. 12 Apr, 2000 1 commit
  26. 14 Mar, 2000 1 commit
    • Thomas G. Lockhart's avatar
      Implement column aliases on views "CREATE VIEW name (collist)". · 64568100
      Thomas G. Lockhart authored
      Implement TIME WITH TIME ZONE type (timetz internal type).
      Remap length() for character strings to CHAR_LENGTH() for SQL92
       and to remove the ambiguity with geometric length() functions.
      Keep length() for character strings for backward compatibility.
      Shrink stored views by removing internal column name list from visible rte.
      Implement min(), max() for time and timetz data types.
      Implement conversion of TIME to INTERVAL.
      Implement abs(), mod(), fac() for the int8 data type.
      Rename some math functions to generic names:
       round(), sqrt(), cbrt(), pow(), etc.
      Rename NUMERIC power() function to pow().
      Fix int2 factorial to calculate result in int4.
      Enhance the Oracle compatibility function translate() to work with string
       arguments (from Edwin Ramirez).
      Modify pg_proc system table to remove OID holes.
      64568100
  27. 09 Mar, 2000 1 commit
  28. 15 Feb, 2000 1 commit
  29. 26 Jan, 2000 1 commit
    • Bruce Momjian's avatar
      Add: · 5c25d602
      Bruce Momjian authored
        * Portions Copyright (c) 1996-2000, PostgreSQL, Inc
      
      to all files copyright Regents of Berkeley.  Man, that's a lot of files.
      5c25d602
  30. 17 Jan, 2000 2 commits
  31. 10 Jan, 2000 1 commit
  32. 10 Dec, 1999 1 commit
  33. 22 Nov, 1999 1 commit
  34. 07 Nov, 1999 1 commit
  35. 01 Nov, 1999 1 commit
  36. 19 Jul, 1999 1 commit
    • Tom Lane's avatar
      Rewrite parser's handling of INSERT ... SELECT so that processing · 7f76eab1
      Tom Lane authored
      of the SELECT part of the statement is just like a plain SELECT.  All
      INSERT-specific processing happens after the SELECT parsing is done.
      This eliminates many problems, e.g. INSERT ... SELECT ... GROUP BY using
      the wrong column labels.  Ensure that DEFAULT clauses are coerced to
      the target column type, whether or not stored clause produces the right
      type.  Substantial cleanup of parser's array support.
      7f76eab1
  37. 17 Jul, 1999 1 commit
  38. 16 Jul, 1999 1 commit
  39. 15 Jul, 1999 1 commit