summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy/dialects/mssql/pyodbc.py
Commit message (Collapse)AuthorAgeFilesLines
* - add notes for pyodbc limitations with rowcount fixes #3675Mike Bayer2016-03-151-0/+7
|
* - happy new yearMike Bayer2016-01-291-1/+1
|
* - Fixed issue when using :class:`.VARBINARY` type in conjunction withMike Bayer2015-06-221-2/+20
| | | | | | | | | an INSERT of NULL + pyodbc; pyodbc requires a special object be passed in order to persist NULL. As the :class:`.VARBINARY` type is now usually the default for :class:`.LargeBinary` due to :ticket:`3039`, this issue is partially a regression in 1.0. The pymssql driver appears to be unaffected. fixes #3464
* - copyright 2015Mike Bayer2015-03-101-1/+1
|
* - The hostname-based connection format for SQL Server when usingMike Bayer2014-09-031-53/+34
| | | | | | | | pyodbc will no longer specify a default "driver name", and a warning is emitted if this is missing. The optimal driver name for SQL Server changes frequently and is per-platform, so hostname based connections need to specify this. DSN-based connections are preferred. fixes #3182
* - apply pep8 formatting to sqlalchemy/sql, sqlalchemy/util, sqlalchemy/dialects,Brian Jarrett2014-07-201-29/+33
| | | | sqlalchemy/orm, sqlalchemy/event, sqlalchemy/testing
* - In the SQL Server pyodbc dialect, repaired the implementationMike Bayer2014-07-141-1/+2
| | | | | | | | | for the ``description_encoding`` dialect parameter, which when not explicitly set was preventing cursor.description from being parsed correctly in the case of result sets that contained names in alternate encodings. This parameter shouldn't be needed going forward. fixes #3091
* - break up the <authors> copyright comment as part of a passMike Bayer2014-07-091-1/+2
| | | | to get all flake8 passing
* - happy new yearMike Bayer2014-01-051-1/+1
|
* - apply a similar fix for floats to mssql+pyodbc as we did to firebirdMike Bayer2013-12-281-3/+9
| | | | | - wrangle through osx+pyodbc+freetds to get at least test_suite to pass again with mssql+pyodbc. invovled adding some silly requirements
* - the raw 2to3 runMike Bayer2013-04-271-1/+1
| | | | - went through examples/ and cleaned out excess list() calls
* - 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 passDiana Clarke2012-11-201-2/+2
|
* juts a 'expected 2 blank lines' pep8 passDiana Clarke2012-11-191-0/+1
|
* - rework the sphinx customizations into distinct modulesMike Bayer2012-10-191-8/+8
| | | | | | | - 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
* finished fixes for mxodbc; need to use at least version 3.2.1Mike Bayer2012-09-211-3/+2
|
* - fixes for mxODBC, some pyodbcMike Bayer2012-09-021-1/+1
| | | | | | - 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
* - more import cleanup for MSSQLMike Bayer2012-08-071-4/+4
|
* -whitespace bonanza, contdMike Bayer2012-07-281-11/+11
|
* Add some `Sphinx` paragraph level versions informations markups,Mike Bayer2012-06-081-1/+4
| | | | such as ``.. versionadded::``, ``.. versionchanged::`` and ``.. deprecated::``.
* - [bug] Repaired the use_scope_identityMike Bayer2012-04-051-1/+2
| | | | | | | | | | create_engine() flag when using the pyodbc dialect. Previously this flag would be ignored if set to False. When set to False, you'll get "SELECT @@identity" after each INSERT to get at the last inserted ID, for those tables which have "implicit_returning" set to False.
* - sqlMike Bayer2012-04-011-0/+25
| | | | | | | | | | | | | | | - [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-041-1/+1
|
* update pyodbc/SQL server connection strings, [ticket:2217]Mike Bayer2011-12-061-8/+12
|
* - [bug] pyodbc-based dialects now parse theMike Bayer2011-12-041-1/+1
| | | | | | | | 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]
* - whitespace removal bonanzaMike Bayer2011-01-021-19/+19
|
* - clean up copyright, update for 2011, stamp every file withMike Bayer2011-01-021-0/+6
| | | | | a consistent tag - AUTHORS file
* - support for cdecimalMike Bayer2010-12-111-8/+19
| | | | | | | | | | | | | | | | | | - 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-031-9/+16
|
* documentation updatesMike Bayer2010-03-281-0/+3
|
* - pymssql now works again, expecting at least the 1.0 series.Mike Bayer2010-03-201-4/+63
|
* try < 0Mike Bayer2010-03-191-2/+2
|
* re-split PyODBCNumeric among Sybase and MS-SQL, they can't be shared.Mike Bayer2010-03-191-3/+53
| | | | | MS-SQL really needs the pure string approach else crashes occur on windows.
* still poking at numericsMike Bayer2010-03-191-1/+2
|
* switching Decimal treatment in MSSQL to be pyodbc specific, addedMike Bayer2010-03-191-5/+13
| | | | | | to connector to share between sybase/mssql. Going with turning decimals with very low significant digit to floats, seems to work so far.
* - added pyodbc for sybase driver.Mike Bayer2010-03-171-0/+13
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - 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).
* | - basic sybase+pyodbc support. in particular this will impact freetds ↵Mike Bayer2010-03-171-15/+0
|/ | | | detection for MS-SQL as well.
* Added a non-freetds specific exclusion for pyodbcMike Bayer2010-03-111-3/+3
|
* mxodbc supports rowcount, just have to snag before the cursor is closed.Mike Bayer2010-02-281-2/+0
|
* working on pyodbc / mxodbcMike Bayer2010-02-271-1/+2
|
* merge 0.6 series to trunk.Mike Bayer2009-08-061-0/+79