1. 25 8月, 2006 3 次提交
  2. 24 8月, 2006 8 次提交
  3. 23 8月, 2006 5 次提交
  4. 22 8月, 2006 11 次提交
  5. 21 8月, 2006 6 次提交
    • B
      Done: · 1054c380
      Bruce Momjian 提交于
      < 	o Add a function to support Parse/DescribeStatement capability
      > 	o -Add a function to support Parse/DescribeStatement capability
      1054c380
    • B
      Remove items, not needed anymore: · fe5d2133
      Bruce Momjian 提交于
      < * %Disallow changing DEFAULT expression of a SERIAL column?
      <
      <   This should be done only if the existing SERIAL problems cannot be
      <   fixed.
      <
      < * %Disallow ALTER SEQUENCE changes for SERIAL sequences because pg_dump
      <   does not dump the changes
      fe5d2133
    • M
      333bc29f
    • T
      Fix all known problems with pg_dump's handling of serial sequences · 2b2a5072
      Tom Lane 提交于
      by abandoning the idea that it should say SERIAL in the dump.  Instead,
      dump serial sequences and column defaults just like regular ones.
      Add a new backend command ALTER SEQUENCE OWNED BY to let pg_dump recreate
      the sequence-to-column dependency that was formerly created "behind the
      scenes" by SERIAL.  This restores SERIAL to being truly "just a macro"
      consisting of component operations that can be stated explicitly in SQL.
      Furthermore, the new command allows sequence ownership to be reassigned,
      so that old mistakes can be cleaned up.
      
      Also, downgrade the OWNED-BY dependency from INTERNAL to AUTO, since there
      is no longer any very compelling argument why the sequence couldn't be
      dropped while keeping the column.  (This forces initdb, to be sure the
      right kinds of dependencies are in there.)
      
      Along the way, add checks to prevent ALTER OWNER or SET SCHEMA on an
      owned sequence; you can now only do this indirectly by changing the
      owning table's owner or schema.  This is an oversight in previous
      releases, but probably not worth back-patching.
      2b2a5072
    • A
      Fix DROP OWNED BY to correctly consider the implicitly-deleted objects list for · df18c51f
      Alvaro Herrera 提交于
      each object to be deleted, instead of the previous hack that just skipped
      INTERNAL dependencies, which didn't really work.  Per report from Tom Lane.
      
      To do this, introduce a new performMultipleDeletions entry point in
      dependency.c to delete multiple objects at once.  The dependency code then has
      the responsability of tracking INTERNAL and AUTO dependencies as needed.
      
      Along the way, change ObjectAddresses so that we can allocate an ObjectAddress
      list from outside dependency.c and not have to export the internal
      representation.
      df18c51f
    • M
  6. 19 8月, 2006 7 次提交