Changeset 389 for trunk/docs

Dec 4, 2008, 9:05:28 PM (11 years ago)

Support for composite primary keys, code clean-up in get(), insert(), update(), clear() and delete() methods.

3 edited


  • trunk/docs/changelog.txt

    r387 r389  
    3737- Added "protocol_version" and "server_version" attributes.
    3838- Revived the "user" attribute.
     39- The pg module now works correctly with composite primary keys;
     40  these are represented as frozensets.
    3941- Removed the undocumented and actually unnecessary "view" parameter
    4042  from the get() method.
     43- get() raises a nicer ProgrammingError instead of a KeyError
     44  if no primary key was found.
    4246Version 3.8.1 (2006-06-05)
  • trunk/docs/future.txt

    r383 r389  
    1111- The insert() method in pg should use a `returning *` clause instead of
    1212  the subsequent get() when the PostgreSQL version is >= 8.2.
    13 - Support composite primary keys and generally reconsider the pkey() method,
    14   (see,
     13- Before getting the values back after insert() and update(), check
     14  with has_table_privilege(table, 'select') whether this is possible.
     15  Otherwise we might break an ongoing transaction.
    1616- Documentation for the pgdb module (everything specific to PyGreSQL).
    1717- The large object and direct access functions need much more attention.
  • trunk/docs/pg.txt

    r384 r389  
    779   This method returns the primary key of a table. Note that this raises
    780   an exception if the table does not have a primary key.
     779  This method returns the primary key of a table. For composite primary
     780  keys, the return value will be a frozenset. Note that this raises an
     781  exception if the table does not have a primary key.
    782783get_databases - get list of databases in the system
    862863  This method is the basic mechanism to get a single row. It assumes
    863   that the key specifies a unique row. If keyname is not specified
     864  that the key specifies a unique row. If `keyname` is not specified
    864865  then the primary key for the table is used. If `arg` is a dictionary
    865866  then the value for the key is taken from it and it is modified to
    866867  include the new values, replacing existing values where necessary.
     868  For a composite key, `keyname` can also be a sequence of key names.
    867869  The OID is also put into the dictionary if the table has one, but in
    868870  order to allow the caller to work with multiple tables, it is munged
Note: See TracChangeset for help on using the changeset viewer.