summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy/dialects/postgresql/pg8000.py
Commit message (Collapse)AuthorAgeFilesLines
...
* pg8000 now supports sane_multi_rowcountpr/125Tony Locke2014-08-021-1/+1
| | | | | From pg8000-1.9.14 sane_multi_rowcount is supported so this commit updates the dialect accordingly.
* Remove spurious print statements in pg8000 dialectTony Locke2014-08-021-2/+0
|
* Merge remote-tracking branch 'origin/pr/117' into pg8000Mike Bayer2014-07-251-0/+19
|\
| * Fix support for two phase commit in pg8000 dialectTony Locke2014-07-191-0/+19
| | | | | | | | | | | | | | The postgresql base dialect has problems with two-phase commit because there isn't a standard way of handling autocommit in DBAPI. This commit modifies the pg8000 dialect to use the DBAPI tpc extension, which is supported by pg8000 as of version 1.9.11.
* | - Fixed bug introduced in 0.9.5 by new pg8000 isolation level featureMike Bayer2014-07-211-2/+6
| | | | | | | | | | where engine-level isolation level parameter would raise an error on connect. fixes #3134
* | - apply pep8 formatting to sqlalchemy/sql, sqlalchemy/util, sqlalchemy/dialects,Brian Jarrett2014-07-201-1/+1
|/ | | | sqlalchemy/orm, sqlalchemy/event, sqlalchemy/testing
* - clarify that the pg8000 backend has no impact of any kind onMike Bayer2014-07-041-8/+9
| | | | the pg8000 DBAPI's encoding behavior, fixes #3112.
* - changelog + docs for pg8000 transaction isolation levelMike Bayer2014-05-301-0/+24
|
* PEP 8 tidy of pg8000 dialect and postgresql/test_dialect.pypr/88Tony Locke2014-05-221-14/+11
|
* Autocommit isolation level for postgresql+pg8000Tony Locke2014-05-221-0/+24
| | | | | | | | As with postgresql+psycopg2, execution_options(isolation_level='AUTOCOMMIT') now works for the postgresql+pg8000 dialect. Also enabled the autocommit test in test_dialect.py for pg8000.
* Updated doc string for postgresql+pg8000 dialectTony Locke2014-05-211-10/+8
|
* pg8000.dbapi is now just pg8000Tony Locke2014-05-211-1/+1
|
* - happy new yearMike Bayer2014-01-051-1/+1
|
* pg8000 fix for decimal return scaleMike Bayer2013-11-231-1/+2
|
* - The precision used when coercing a returned floating point value toMike Bayer2013-11-221-1/+2
| | | | | | | | | | Python ``Decimal`` via string is now configurable. The flag ``decimal_return_scale`` is now supported by all :class:`.Numeric` and :class:`.Float` types, which will ensure this many digits are taken from the native floating point value when it is converted to string. If not present, the type will make use of the value of ``.scale``, if the type supports this setting and it is non-None. Otherwise the original default length of 10 is used. [ticket:2867]
* - remove all compat items that are pre-2.5 (hooray)Mike Bayer2013-03-091-1/+1
| | | | | | - other cleanup - don't need compat.decimal, that approach never panned out. hopefully outside libs aren't pulling it in, they shouldn't be
* happy new year (see #2645)Diana Clarke2013-01-011-1/+1
|
* just a pep8 pass of lib/sqlalchemy/dialects/postgresqlDiana Clarke2012-11-191-3/+6
|
* - rework the sphinx customizations into distinct modulesMike Bayer2012-10-191-13/+6
| | | | | | | - build a new Sphinx extension that allows dialect info to be entered as directives which is then rendered consistently throughout all dialect/dbapi sections - break out the "empty_strings" requirement for oracle test
* - move out maxdbMike Bayer2012-10-181-2/+8
| | | | | | - begin consolidating docs for dialects to be more self contained - add a separate section for "external" dialects - not sure how we're going to go with this yet.
* - update all the visit_mod() functions with new naming schemeMike Bayer2012-08-141-2/+3
| | | | | | - visit_mods all seemed to not propagate **kw down to process(). this is [ticket:2548] which may be backported to 0.7 pending a test case to illustrate wrong behavior.
* more import cleanupsMike Bayer2012-08-071-5/+5
|
* happy new yearMike Bayer2012-01-041-1/+1
|
* - Fixed support for precision numerics when usingMike Bayer2011-04-141-1/+7
| | | | pg8000. [ticket:2132]
* - assume in py3k that description encoding is None unless the dialect reallyMike Bayer2011-04-081-0/+1
| | | | | overrides it - psycopg2 + 3k supports unicode statements...
* - add connection and cursor to is_disconnect(). We aren't using it yet,Mike Bayer2011-02-091-1/+1
| | | | | | | | | | | | | | | but we'd like to. Most DBAPIs don't give us anything we can do with it. Some research was done on psycopg2 and it still seems like they give us no adequate method (tried connection.closed, cursor.closed, connection.status). mxodbc claims their .closed attribute will work (but I am skeptical). - remove beahvior in pool that auto-invalidated a connection when the cursor failed to create. That's not the pool's job. we need the conn for the error logic. Can't get any tests to fail, curious why that behavior was there, guess we'll find out (or not). - add support for psycopg2 version detection. even though we have no use for it yet... - adjust one of the reconnect tests to work with oracle's horrendously slow connect speed
* - whitespace removal bonanzaMike Bayer2011-01-021-5/+5
|
* - clean up copyright, update for 2011, stamp every file withMike Bayer2011-01-021-0/+6
| | | | | a consistent tag - AUTHORS file
* Ridding the world of a few wasteful imports.Michael Trier2010-12-191-1/+0
|
* - support for cdecimalMike Bayer2010-12-111-2/+1
| | | | | | | | | | | | | | | | | | - add --with-cdecimal flag to tests, monkeypatches cdecimal in - fix mssql/pyodbc.py to not use private '_int' accessor in decimal conversion routines - pyodbc version 2.1.8 is needed for cdecimal in any case as previous versions also called '_int', 2.1.8 adds the same string logic as our own dialect, so that logic is skipped for modern pyodbc version - make the imports for "Decimal" consistent across the whole lib. not sure yet how we should be importing "Decimal" or what the best way forward is that would allow a clean user-invoked swap of cdecimal; for now, added docs suggesting a global monkeypatch - the two decimal libs are not compatible with each other so any chance of mixing produces serious issues. adding adapters to DBAPIs tedious and adds in-python overhead. suggestions welcome on how we should be doing Decimal/cdecimal.
* - Ensured every numeric, float, int code, scalar + array,Mike Bayer2010-11-181-9/+13
| | | | | are recognized by psycopg2 and pg8000's "numeric" base type. [ticket:1955]
* - PG doc updatesMike Bayer2010-07-131-1/+1
| | | | | | - pypostgresql has 15 errors, 3 failures, this probably puts it in the "yes" as opposed to the "partial" support category. [ticket:1850]
* - fixed numeric test for pg8000, factored out decimal/float codesMike Bayer2010-04-091-5/+6
|
* - Repaired missing import in psycopg2._PGNumeric type whenMike Bayer2010-04-071-4/+4
| | | | | | | | | | | unknown numeric is received. - psycopg2/pg8000 dialects now aware of REAL[], FLOAT[], DOUBLE_PRECISION[], NUMERIC[] return types without raising an exception. - introducing testing.provide_metadata for all these stupid little create/drop tests
* don't seem to need bind processing for pg8000 decimals.Mike Bayer2010-03-191-3/+0
|
* - name all the "sub" dialect components <DB><component>_<dialectname>, ↵Mike Bayer2010-03-141-8/+8
| | | | [ticket:1738]
* - Added an optional C extension to speed up the sql layer byGaëtan de Menten2010-02-131-19/+6
| | | | | | | | | | | | | | | reimplementing the highest impact functions. The actual speedups will depend heavily on your DBAPI and the mix of datatypes used in your tables, and can vary from a 50% improvement to more than 200%. It also provides a modest (~20%) indirect improvement to ORM speed for large queries. Note that it is *not* built/installed by default. See README for installation instructions. - The most common result processors conversion function were moved to the new "processors" module. Dialect authors are encouraged to use those functions whenever they correspond to their needs instead of implementing custom ones.
* - pg8000 + postgresql dialects now check for float/numeric returnMike Bayer2009-11-151-14/+35
| | | | | | | | | | types to more intelligently determine float() vs. Decimal(), [ticket:1567] - since result processing is a hot issue of late, the DBAPI type returned from cursor.description is certainly useful in cases like these to determine an efficient result processor. There's likely other result processors that can make use of it. But, backwards incompat change to result_processor(). Happy major version number..
* - DefaultRunner and subclasses have been removed. The jobMike Bayer2009-10-151-2/+2
| | | | | | | of this object has been simplified and moved into ExecutionContext. Dialects which support sequences should add a `fire_sequence()` method to their execution context implementation. [ticket:1566]
* correct the create_engine urlPhilip Jenvey2009-08-261-1/+2
| | | | | fixes #1515 thanks Randall
* move postgresql's % escape handling out of basePhilip Jenvey2009-08-111-2/+17
|
* merge 0.6 series to trunk.Mike Bayer2009-08-061-0/+84
View Lorry Controller Status