summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy/connectors
Commit message (Collapse)AuthorAgeFilesLines
* - happy new yearMike Bayer2014-01-055-5/+5
|
* - add copyright to source files missing itMike Bayer2013-10-261-0/+6
|
* - some tweaks to try to help out mssql+pyodbc support a bit, py3k is reallyMike Bayer2013-06-031-12/+19
| | | | not happening too well (I need to stick with linux + freetds 0.91, I know)
* work through dialectsMike Bayer2013-04-271-16/+13
|
* - the raw 2to3 runMike Bayer2013-04-272-14/+14
| | | | - went through examples/ and cleaned out excess list() calls
* happy new year (see #2645)Diana Clarke2013-01-014-4/+4
|
* just a pep8 pass of lib/sqlalchemy/connectorsDiana Clarke2012-11-195-17/+27
|
* - [feature] Added "read_timeout" flag to MySQLdbMike Bayer2012-10-101-0/+1
| | | | dialect. [ticket:2554]
* finished fixes for mxodbc; need to use at least version 3.2.1Mike Bayer2012-09-211-14/+5
|
* - further mxodbc tweaks affecting other test suitesMike Bayer2012-09-021-1/+0
|
* - leave this out for nowMike Bayer2012-09-021-2/+2
|
* - fixes for mxODBC, some pyodbcMike Bayer2012-09-021-8/+15
| | | | | | - enhancements to test suite including ability to set up a testing engine for a whole test class, fixes to how noseplugin sets up/tears down per-class context
* - 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.
* -whitespace bonanza, contdMike Bayer2012-07-283-9/+9
|
* - absolute imports in connectors, databasesMike Bayer2012-06-234-9/+8
|
* - sqlMike Bayer2012-04-011-2/+10
| | | | | | | | | | | | | | | - [bug] Removed warning when Index is created with no columns; while this might not be what the user intended, it is a valid use case as an Index could be a placeholder for just an index of a certain name. - mssql - [feature] Added interim create_engine flag supports_unicode_binds to PyODBC dialect, to force whether or not the dialect passes Python unicode literals to PyODBC or not.
* happy new yearMike Bayer2012-01-044-4/+4
|
* - [bug] pyodbc-based dialects now parse theMike Bayer2011-12-041-0/+17
| | | | | | | | pyodbc accurately as far as observed pyodbc strings, including such gems as "py3-3.0.1-beta4" [ticket:2318] - [bug] use new pyodbc version detection for _need_decimal_fix option, [ticket:2318]
* - Changes to attempt support of FreeTDS 0.91 withMike Bayer2011-09-181-1/+9
| | | | | | | | | | | | | Pyodbc. This includes that string binds are sent as Python unicode objects when FreeTDS 0.91 is detected, and a CAST(? AS NVARCHAR) is used when we detect for a table. However, I'd continue to characterize Pyodbc + FreeTDS 0.91 behavior as pretty crappy, there are still many queries such as used in reflection which cause a core dump on Linux, and it is not really usable at all on OSX, MemoryErrors abound and just plain broken unicode support. [ticket:2273]
* - Adjusted the pyodbc dialect such that boundMike Bayer2011-06-061-4/+10
| | | | | | | | | values are passed as bytes and not unicode if the "Easysoft" unix drivers are detected. This is the same behavior as occurs with FreeTDS. Easysoft appears to segfault if Python unicodes are passed under certain circumstances.
* - Unit tests pass 100% on MySQL installedMike Bayer2011-06-021-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | on windows, after aggressive exclusion of a wide variety of tests. Not clear to what degree the failures are related to version 5.5 vs. the usage of windows, in particular the ON UPDATE CASCADE immediately crashes the server. The features being tested here are all edge cases not likely to be used in typical MySQL environments. - Removed the "adjust casing" step that would fail when reflecting a table on MySQL on windows with a mixed case name. After some experimenting with a windows MySQL server, it's been determined that this step wasn't really helping the situation much; MySQL does not return FK names with proper casing on non-windows platforms either, and removing the step at least allows the reflection to act more like it does on other OSes. A warning here has been considered but its difficult to determine under what conditions such a warning can be raised, so punted on that for now - added some docs instead. [ticket:2181] - supports_sane_rowcount will be set to False if using MySQLdb and the DBAPI doesn't provide the constants.CLIENT module.
* - add connection and cursor to is_disconnect(). We aren't using it yet,Mike Bayer2011-02-093-5/+5
| | | | | | | | | | | | | | | 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
* - SchemaItem, SchemaType now descend from common typeMike Bayer2011-01-301-4/+7
| | | | | | | | | | | | | | | | | | SchemaEventTarget, which supplies dispatch - the dispatch now provides before_parent_attach(), after_parent_attach(), events which generally bound the _set_parent() event. [ticket:2037] - the _on_table_attach mechanism now usually uses the event dispatch - fixed class-level event dispatch to propagate to all subclasses, not just immediate subclasses - fixed class-level event unpickling to handle more involved inheritance hierarchies, needed by the new schema event dispatch. - ForeignKeyConstraint doesn't re-call the column attach event on ForeignKey objects that are already associated with the correct Column - we still need that ImportError on mysqldb CLIENT FLAGS to support mock DBAPIs
* fix this to work on 2.4Mike Bayer2011-01-261-7/+4
|
* - New DBAPI support for pymysql, a pure Python portMike Bayer2011-01-261-1/+4
| | | | of MySQL-python. [ticket:1991]
* - new dialect for Drizzle [ticket:2003]Mike Bayer2011-01-261-0/+147
| | | | - move mysqldb to a connector, can be shared among mysql/drizzle
* - whitespace removal bonanzaMike Bayer2011-01-024-20/+19
|
* - clean up copyright, update for 2011, stamp every file withMike Bayer2011-01-024-0/+23
| | | | | a consistent tag - AUTHORS file
* Ridding the world of a few wasteful imports.Michael Trier2010-12-192-4/+0
|
* - support for cdecimalMike Bayer2010-12-111-1/+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.
* - idle 78-char adjustmentsMike Bayer2010-07-033-12/+23
|
* documentation updatesMike Bayer2010-03-281-0/+1
|
* mssql+mxodbc should use executedirect for all selects and execute for ↵Mike Bayer2010-03-261-10/+20
| | | | insert/update/delete. To support this, an is_crud property has been added to the DefaultExecutionContext. The behavior is forcable either way per execution using execution_options(native_odbc_parameters=True|False). Some tests have been added to demonstrate usage. (patch by zzzeek committed by bradallen)
* whitespace tweaksBrad Allen2010-03-201-2/+1
|
* For cases when mxODBC's cursor.execute can't do the job, raise a warning and ↵Brad Allen2010-03-201-1/+8
| | | | fall back on cursor.executedirect which is less picky. This causes a drastic improvement in passing tests.
* now loading mxODBC exception classes into module namespace while still ↵Brad Allen2010-03-201-0/+13
| | | | avoiding module imports (hooking into dbapi class method)
* added comment about alternative way to get server version infoBrad Allen2010-03-201-0/+1
|
* re-split PyODBCNumeric among Sybase and MS-SQL, they can't be shared.Mike Bayer2010-03-191-43/+0
| | | | | MS-SQL really needs the pure string approach else crashes occur on windows.
* still poking at numericsMike Bayer2010-03-191-1/+4
|
* - the string approach appears to be necessary for large numbers, however.Mike Bayer2010-03-191-38/+26
| | | | Don't know how to get large decimals through to Sybase.
* switching Decimal treatment in MSSQL to be pyodbc specific, addedMike Bayer2010-03-191-0/+53
| | | | | | to connector to share between sybase/mssql. Going with turning decimals with very low significant digit to floats, seems to work so far.
* Removed MxNumeric and MxFloat because now the sqlalchemy.types base classes ↵Brad Allen2010-03-181-53/+0
| | | | support dialects having a class attribute of "supports_native_decimal" indicating native Python Demimal support. Adjusted mssql+mxodbc to use the sqlalchemy.types base classes for Float and Numeric instead of using the base mssql dialect's numeric types.
* removed mxODBC imports from the module levelBrad Allen2010-03-181-3/+0
|
* Merged from main tip.Brad Allen2010-03-181-1/+2
|\
| * - moved most Decimal bind/result handling into types.py, out of sqlite, ↵Mike Bayer2010-03-181-1/+2
| | | | | | | | | | | | | | mysql dialects. - added an explicit test for [ticket:1216] - some questions remain about MSSQL - would like to simplify/remove bind handling for numerics
* | comments/question about using connection.closed in is_disconnect methodBrad Allen2010-03-181-0/+2
| |
* | Docstring improvements for MxDecimal and MxNumeric result processors.Brad Allen2010-03-181-2/+12
| |
* | eGenix says "It's better to let mxODBC decide which bind type to use."Brad Allen2010-03-181-3/+0
| |
* | Merged from main tip, and resolved conflicts in mxodbc dialect and connector.Brad Allen2010-03-172-16/+43
|\ \ | |/
| * - added pyodbc for sybase driver.Mike Bayer2010-03-171-5/+0
| |\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - generalized the "freetds" / "unicode statements" behavior of MS-SQL/pyodbc into the base Pyodbc connector, as this seems to apply to Sybase as well. - generalized the python-sybase "use autocommit for DDL" into the pyodbc connector. With pyodbc, the "autocommit" flag on connection is used, as Pyodbc seems to have more database conversation than python-sybase that can't otherwise be suppressed. - Some platforms will now interpret certain literal values as non-bind parameters, rendered literally into the SQL statement. This to support strict SQL-92 rules that are enforced by some platforms including MS-SQL and Sybase. In this model, bind parameters aren't allowed in the columns clause of a SELECT, nor are certain ambiguous expressions like "?=?". When this mode is enabled, the base compiler will render the binds as inline literals, but only across strings and numeric values. Other types such as dates will raise an error, unless the dialect subclass defines a literal rendering function for those. The bind parameter must have an embedded literal value already or an error is raised (i.e. won't work with straight bindparam('x')). Dialects can also expand upon the areas where binds are not accepted, such as within argument lists of functions (which don't work on MS-SQL when native SQL binding is used).
View Lorry Controller Status