summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| | * | | Mention context managers in NEWS fileDaniele Varrazzo2012-12-041-0/+2
| | | | |
| | * | | Make sure to call subclasses methods on context exitDaniele Varrazzo2012-12-033-3/+64
| | | | |
| | * | | Added documentation for the with statementDaniele Varrazzo2012-12-033-0/+37
| | | | |
| | * | | Added support for with statement for connection and cursorDaniele Varrazzo2012-12-034-0/+250
| | | | | | | | | | | | | | | | | | | | | | | | | The implementation should be conform to the DBAPI, although the "with" extension has not been released yet.
| | * | | Fixed signature for METH_NOARGS functionsDaniele Varrazzo2012-12-032-17/+17
| | | |/ | | |/|
| * | | Merge branch 'zope-fixes' into develDaniele Varrazzo2012-12-047-13/+175
| |\ \ \
| | * | | Fixed connections re-init across ZSQL methodsDaniele Varrazzo2012-12-042-4/+5
| | | | | | | | | | | | | | | | | | | | Fixes issue #142, probably #123 and #125 too.
| | * | | Added specific pool implementation for ZPsycopgDADaniele Varrazzo2012-12-042-3/+151
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The implementation is based on psycopg 2.4, which should be less broken (zope-wise) of the current one. Instantiating psycopg2.pool.PersistentConnectionPool now raises a warning. This should fix ticket #123, #125. The issue of the reset on set_client_encoding() is still present but that's always been there and I'm no good at fixing it.
| | * | | Use set_session instead of set_isolation_level where availableDaniele Varrazzo2012-12-041-4/+9
| | | | | | | | | | | | | | | | | | | | Avoid spurious queries as reported in psycopg2 ticket #125.
| | * | | Show all the available isolation levels in ZPsycopgDA menuDaniele Varrazzo2012-12-042-1/+9
| | | | |
| | * | | Added 2.4.6 to the allowed versions for ZPsycopgDADaniele Varrazzo2012-12-041-1/+1
| |/ / / | | | | | | | | | | | | | | | | Dropped beta versions and the versions with the messed up isolation level constants.
| * | | Fixed version number in NEWS fileDaniele Varrazzo2012-12-031-1/+1
| | | |
| * | | Fixed empty strings handling in composite casterDaniele Varrazzo2012-12-033-2/+24
| |/ / | | | | | | | | | Closes ticket #141.
| * | Splitting the release of new features in version 2.5Daniele Varrazzo2012-12-035-11/+17
| | |
| * | Release the GIL around PQgetResult calls after COPYDaniele Varrazzo2012-11-242-5/+18
| | | | | | | | | | | | It should fix ticket #140.
| * | Fixed a couple of terms in the docsDaniele Varrazzo2012-11-121-2/+2
| | | | | | | | | | | | After Pierre-Louis Bonicoli's suggestions in ticket #138.
| * | Added note about the adapted attribute in the module-level wrappersDaniele Varrazzo2012-10-271-11/+17
| | | | | | | | | | | | | | | Specifying it otherwise people expects the wrappers to have full datetime semantics: see ticket #136.
| * | Merge branch 'fix-135' into develDaniele Varrazzo2012-10-213-4/+25
| |\ \
| | * | Fixed pickling of FixedOffsetTimezone objectsDaniele Varrazzo2012-10-213-2/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | I have also verified that the fixed class can unpickle instance pickled with the buggy one and viceversa. Fixes ticket #135.
| | * | More idiomatic way to call FixedOffsetTimezone.__new__ superclassDaniele Varrazzo2012-10-211-1/+1
| | | |
| | * | Dropped redundant call to FixedOffsetTimezone.__init__Daniele Varrazzo2012-10-211-1/+0
| |/ /
| * | Clarification in copy_expert docsDaniele Varrazzo2012-10-151-2/+11
| | | | | | | | | | | | Closes ticket #134.
| * | Discard any result produced by cursor.executemany()Daniele Varrazzo2012-10-115-28/+44
| | |
| * | Merge branch 'fix-113' into develDaniele Varrazzo2012-10-117-27/+139
| |\ \
| | * | Close the connection on error in callbackDaniele Varrazzo2012-10-064-61/+69
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Unfortunately PQcancel blocks, so it's not better than PQgetResult. It has been suggested to use PQreset in non-blocking way but this would give the Python program the burden of handling a connection done but not configured in an unexpected place.
| | * | Get the result from the connection after the green panicDaniele Varrazzo2012-10-062-1/+16
| | | | | | | | | | | | | | | | | | | | | | | | Otherwise the connection won't be usable in case we manage to put it back on track (libpq reports "another command is already in progress")
| | * | Added compatibility PyErr_WarnEx macro for Python 2.4Daniele Varrazzo2012-10-061-0/+5
| | | |
| | * | Attempt to fix issue #113.Daniele Varrazzo2012-10-062-15/+88
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If the network is down, trying to read blocking will hang the process hard (ctrl-c not working). Send a cancel signal instead (as suggested in http://archives.postgresql.org/pgsql-hackers/2012-07/msg00903.php) and go back into a green polling: this should allow a further error (e.g. another ctrl-c) to break the loop. In this case we cannot assume anything about the state of the connection, so we close it.
| | * | Added function conn_close_locked()Daniele Varrazzo2012-10-062-7/+18
| | | |
| * | | Copyright bumped to 2012 in docs pagesDaniele Varrazzo2012-10-071-1/+1
| | | |
| * | | Docs front page adjustmentsDaniele Varrazzo2012-10-071-12/+14
| | | |
| * | | Added install section to the manualDaniele Varrazzo2012-10-074-0/+269
| | | |
| * | | Dropped compiler warning on Py 2.4Daniele Varrazzo2012-10-061-0/+6
| |/ /
| * | Using super() in the connection/cursor subclassesDaniele Varrazzo2012-09-281-29/+28
| | | | | | | | | | | | | | | This opens to collaborative subclassing (e.g. you may want to have a logging namedtuple cursor...)
| * | Merge branch 'range-type' into develDaniele Varrazzo2012-09-275-1/+1051
| |\ \
| | * | More helpful error messasge on Range order attemptsDaniele Varrazzo2012-09-251-1/+3
| | | |
| | * | Grammar correction for RangeCaster.array_typecasterDaniele Varrazzo2012-09-241-1/+1
| | | |
| | * | Added documentation for range types and adaptationDaniele Varrazzo2012-09-243-35/+128
| | | |
| | * | Don't need to implement __new__ to make an immutable classDaniele Varrazzo2012-09-241-4/+1
| | | |
| | * | Fixed search of types into schemas.Daniele Varrazzo2012-09-242-3/+30
| | | | | | | | | | | | | | | | | | | | | | | | We don't need to look for stuff implicitly into pg_catalog as all the builtin ranges are already registered. So just search into 'public' if the schema is not specified.
| | * | Added test for range not foundDaniele Varrazzo2012-09-241-0/+6
| | | |
| | * | Added containment tests for unbounded intervalsDaniele Varrazzo2012-09-231-0/+23
| | | |
| | * | Range objects cannot be orderedDaniele Varrazzo2012-09-232-0/+12
| | | |
| | * | Range objects are nonzero when not emptyDaniele Varrazzo2012-09-232-0/+9
| | | |
| | * | Range objects are immutable and hashableDaniele Varrazzo2012-09-232-1/+35
| | | |
| | * | Dropped Range._empty attributeDaniele Varrazzo2012-09-231-13/+13
| | | | | | | | | | | | | | | | | | | | We can do with just _bounds: it will make eq and hash easier to implement in a consistent way
| | * | Added in operator for rangesDaniele Varrazzo2012-09-232-0/+45
| | | |
| | * | NumberRange renamed to NumericRangeDaniele Varrazzo2012-09-233-25/+25
| | | | | | | | | | | | | | | | | | | | | | | | I was avoiding Numeric to avoid conflicting with the 'numeric' Postgres type, which is an alias for 'decimal'. But now that there is a single numeric range I can use the preferred name
| | * | Dropped Range classes for specific numeric typesDaniele Varrazzo2012-09-233-23/+10
| | | |
| | * | Added first implementation of Range type, adapter, typecasterDaniele Varrazzo2012-09-233-5/+816
| | | |
View Lorry Controller Status