summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy/dialects/sybase/pyodbc.py
Commit message (Collapse)AuthorAgeFilesLines
* - copyright 2015Mike Bayer2015-03-101-1/+1
|
* - apply pep8 formatting to sqlalchemy/sql, sqlalchemy/util, sqlalchemy/dialects,Brian Jarrett2014-07-201-3/+4
| | | | sqlalchemy/orm, sqlalchemy/event, sqlalchemy/testing
* - 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
|
* - 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/sybaseDiana Clarke2012-11-191-3/+6
|
* - rework the sphinx customizations into distinct modulesMike Bayer2012-10-191-7/+5
| | | | | | | - 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
* -whitespace bonanza, contdMike Bayer2012-07-281-2/+2
|
* happy new yearMike Bayer2012-01-041-1/+1
|
* - whitespace removal bonanzaMike Bayer2011-01-021-3/+3
|
* - 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-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.
* 78 chars for sybaseMike Bayer2010-07-061-2/+4
|
* re-split PyODBCNumeric among Sybase and MS-SQL, they can't be shared.Mike Bayer2010-03-191-6/+26
| | | | | MS-SQL really needs the pure string approach else crashes occur on windows.
* still poking at numericsMike Bayer2010-03-191-1/+1
|
* switching Decimal treatment in MSSQL to be pyodbc specific, addedMike Bayer2010-03-191-22/+6
| | | | | | to connector to share between sybase/mssql. Going with turning decimals with very low significant digit to floats, seems to work so far.
* turning the decimals to floats allows the E notation to work with ↵Mike Bayer2010-03-181-0/+26
| | | | sybase+pyodbc for small E notations
* - pyodbc can do *some* unicode with sybase, python-sybase not at all.Mike Bayer2010-03-171-0/+17
| | | | | Since python-sybase source code seems to be all from 2001 with no updates, making pyodbc the default driver.
* - added pyodbc for sybase driver.Mike Bayer2010-03-171-1/+6
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - 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-1/+5
|/ | | | detection for MS-SQL as well.
* - name all the "sub" dialect components <DB><component>_<dialectname>, ↵Mike Bayer2010-03-141-2/+2
| | | | [ticket:1738]
* - initial working version of sybase, with modifications to the transactionalMike Bayer2010-03-141-1/+9
| | | | | | | | | | model to accomodate Sybase's default mode of "no ddl in transactions". - identity insert not working yet. it seems the default here might be the opposite of that of MSSQL. - reflection will be a full rewrite - default DBAPI is python-sybase, well documented and nicely DBAPI compliant except for the bind parameter situation, where we have a straightforward workaround - full Sybase docs at: http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.ase_15.0/title.htm
* merge 0.6 series to trunk.Mike Bayer2009-08-061-0/+11
View Lorry Controller Status