1. 30 Nov, 2002 5 commits
  2. 29 Nov, 2002 4 commits
  3. 28 Nov, 2002 1 commit
  4. 27 Nov, 2002 4 commits
  5. 26 Nov, 2002 10 commits
  6. 25 Nov, 2002 8 commits
    • Bruce Momjian's avatar
      9645fa8c
    • Tom Lane's avatar
      Remove unused constisset and constiscast fields of Const nodes. Clean · f893ee27
      Tom Lane authored
      up code and documentation associated with Param nodes.
      f893ee27
    • Tom Lane's avatar
      Restructure outfuncs and readfuncs to use macros in the same style as · dbe100c4
      Tom Lane authored
      just done for copyfuncs/equalfuncs.  Read functions in particular get
      a lot shorter than before, and it's much easier to compare an out function
      with the corresponding read function to make sure they agree.
      initdb forced due to small changes in nodestring format (regularizing
      a few cases that were formerly idiosyncratic).
      dbe100c4
    • Tom Lane's avatar
      Un-break triggers declared for INSERT OR DELETE OR UPDATE. This worked · 0aa5b686
      Tom Lane authored
      okay in 7.3, so I think it must have been busted in the recent triggers
      patch.
      0aa5b686
    • Tom Lane's avatar
      Restructure the code in copyfuncs and equalfuncs to put much heavier · 2eafcf68
      Tom Lane authored
      reliance on macros, in hopes of eliminating silly typos (like copying
      to the wrong field) and just generally making it easier to see the forest
      instead of the trees.  As an example, here is the new code for A_Indices:
      
      static A_Indices *
      _copyAIndices(A_Indices *from)
      {
      	A_Indices  *newnode = makeNode(A_Indices);
      
      	COPY_NODE_FIELD(lidx);
      	COPY_NODE_FIELD(uidx);
      
      	return newnode;
      }
      
      static bool
      _equalAIndices(A_Indices *a, A_Indices *b)
      {
      	COMPARE_NODE_FIELD(lidx);
      	COMPARE_NODE_FIELD(uidx);
      
      	return true;
      }
      
      I plan to redo outfuncs/readfuncs in a similar style, but am committing
      what I've got.
      2eafcf68
    • D'Arcy J.M. Cain's avatar
      I'm sending you a small patch to pgdb.py module. This · 200dd8e3
      D'Arcy J.M. Cain authored
      raises pgdb.DatabaseError when any of the fetch*
      methods was invoked but previous call to execute* did
      not produce any result set or no call was issued yet.
      Also, raises pgdb.NotSupportedError when .nextset() is
      invoked, instead of NameError.
      
      This behaviour complies with DB-API 2.0.
      
      Thanks for your work!
      
      Timur Irmatov.
      200dd8e3
    • D'Arcy J.M. Cain's avatar
      Change the pkey method so that the caller can optionally set the dictionary · a4bc5eee
      D'Arcy J.M. Cain authored
      used for the primary key lookup.  This will prevent a database lookup
      for each connection object that gets created.  This could be a significant
      optimization on a busy system.
      
      Similarly, the get_attnames method allows for the attributes dictionary
      to be installed directly.
      a4bc5eee
    • D'Arcy J.M. Cain's avatar
      Change the debug variable to allow better control by the caller over how · f393ee06
      D'Arcy J.M. Cain authored
      debug output is managed.  The user can continue to use the current method
      of passing a formatting string to have a replacement done and output will
      be sent to the standard output exactly as it did before.  In addition they
      can set it to a file object, sys.stderr for example, and the query string
      will be printed to it.  Thay can also set it to a method (function) and the
      query string will be passed to that method giving them the maximum flexibility
      to do whatever they want with the query string.
      
      I will be working with the PyGreSQL documentation shortly and at that time
      will properly document this feature.
      f393ee06
  7. 24 Nov, 2002 3 commits
    • Tom Lane's avatar
      Restructure planning of nestloop inner indexscans so that the set of usable · 04c8785c
      Tom Lane authored
      joinclauses is determined accurately for each join.  Formerly, the code only
      considered joinclauses that used all of the rels from the outer side of the
      join; thus for example
      	FROM (a CROSS JOIN b) JOIN c ON (c.f1 = a.x AND c.f2 = b.y)
      could not exploit a two-column index on c(f1,f2), since neither of the
      qual clauses would be in the joininfo list it looked in.  The new code does
      this correctly, and also is able to eliminate redundant clauses, thus fixing
      the problem noted 24-Oct-02 by Hans-Jürgen Schönig.
      04c8785c
    • Bruce Momjian's avatar
      7.4devel now supports SQL:1999's "enhanced trigger capability" (which · 6bfc09ba
      Bruce Momjian authored
      is just FOR EACH STATEMENT triggers, AFAICS); this patch updates the
      SQL conformance docs to note that.
      
      Neil Conway
      6bfc09ba
    • Bruce Momjian's avatar
      Split: · 1676753e
      Bruce Momjian authored
      > * -Support statement-level triggers (Neil)
      > * Support triggers on columns (Neil)
      1676753e
  8. 23 Nov, 2002 5 commits