Changeset 733 for trunk/docs


Ignore:
Timestamp:
Jan 13, 2016, 10:12:48 AM (4 years ago)
Author:
cito
Message:

Assume select privilege in insert/update()

Don't query the database whether we have select privilege on the
table on every call of insert/update(). We assume that we can
update/insert() anyway, and it's pretty sane then to assume we can
select, too. This spares one database request per call that is
superfluous under all normal circumstances. In the theoretically
possible but rare case that you can insert/update and not select,
a normal query() is always possible instead.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/docs/contents/pg/db_wrapper.rst

    r729 r733  
    182182added to or replace the entry in the dictionary.
    183183
    184 The dictionary is then, if possible, reloaded with the values actually
    185 inserted in order to pick up values modified by rules, triggers, etc.
     184The dictionary is then reloaded with the values actually inserted in order
     185to pick up values modified by rules, triggers, etc.
    186186
    187187Note: The method currently doesn't support insert into views
     
    202202Similar to insert but updates an existing row.  The update is based on the
    203203OID value as munged by get or passed as keyword, or on the primary key of
    204 the table.  The dictionary is modified, if possible, to reflect any changes
    205 caused by the update due to triggers, rules, default values, etc.
     204the table.  The dictionary is modified to reflect any changes caused by the
     205update due to triggers, rules, default values, etc.
    206206
    207207Like insert, the dictionary is optional and updates will be performed
Note: See TracChangeset for help on using the changeset viewer.