1. 07 4月, 2003 1 次提交
  2. 13 12月, 2002 1 次提交
    • B
      > There is an ugly little problem with the DB wrapper class. · d2741059
      Bruce Momjian 提交于
      >
      > In pg.py the attributes of DB are defined as being the same as
      > the attributes of the corresponding pgobject "db", using the following
      
      ...
      
      > The problem is that the attributes of db (which are read only)
      > are not static (they are actually function calls to PostgreSQL),
      > especially "status" and "error", but those attributes are copied
      > and this is done only once when initializing the DB object.
      >
      > So, in effect, only the attribute "db.error" of a DB instance
      > will be updated, but not the attribute "error". Same with "status".
      
      
      > Don't copy the (read only) attributes of the pgobject to the
      > DB object, but only the methods, and all of them, like this:
      >
      > --------------- change in pg.py ------------------
      > # Create convience methods, in a way that is still overridable.
      > for e in self.db.__methods__:
      >  setattr(self, e, getattr(self.db, e))
      > ----------------------------------------------------
      >
      > Furthermore, make an addition to the documentation of the
      > DB wrapper class (i.e. in pygresql-pg-db.html):
      > After the sentence "All pgobject methods are included in this class also."
      > add the following sentence "The pgobject read-only attributes can be
      > accessed py adding the prefix 'db.' to them."
      
      Christoph Zwerschke
      d2741059
  3. 24 9月, 2002 2 次提交
  4. 28 3月, 2002 1 次提交
  5. 21 11月, 2001 1 次提交
  6. 19 11月, 2001 1 次提交
  7. 13 9月, 2001 1 次提交
  8. 10 9月, 2001 1 次提交
  9. 05 3月, 2001 1 次提交