summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy/dialects/mssql/base.py
Commit message (Collapse)AuthorAgeFilesLines
...
* - pymssql now works again, expecting at least the 1.0 series.Mike Bayer2010-03-201-113/+1
|
* removed all dialect table_names() methods and standardizedMike Bayer2010-03-191-9/+4
| | | | on get_table_names(). [ticket:1739]
* switching Decimal treatment in MSSQL to be pyodbc specific, addedMike Bayer2010-03-191-64/+7
| | | | | | to connector to share between sybase/mssql. Going with turning decimals with very low significant digit to floats, seems to work so far.
* fixed missing return statement which caused render_literal_value to chokeBrad Allen2010-03-181-1/+1
|
* Added MSSQLStrictCompiler support for rendering datetime typesBrad Allen2010-03-181-3/+17
|
* adjustments to improve readability (indentation to complex conditional ↵Brad Allen2010-03-181-23/+59
| | | | expressions, excessively long lines brokenup). This is only a partial cleanup.
* Hardcoded ident_seed and ident_increment query had bind markers noncompliant ↵Brad Allen2010-03-181-5/+3
| | | | with SQL-92, which caused mxODBC failures. This was corrected by using string substitution in building the statement, and removing the bind params.
* turning the decimals to floats allows the E notation to work with ↵Mike Bayer2010-03-181-1/+2
| | | | sybase+pyodbc for small E notations
* - moved most Decimal bind/result handling into types.py, out of sqlite, ↵Mike Bayer2010-03-181-19/+5
| | | | | | | mysql dialects. - added an explicit test for [ticket:1216] - some questions remain about MSSQL - would like to simplify/remove bind handling for numerics
* some ms fixesMike Bayer2010-03-171-4/+6
|
* - added pyodbc for sybase driver.Mike Bayer2010-03-171-6/+38
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - 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).
| * - mxodbc can use default execute() callMike Bayer2010-03-161-2/+2
|/ | | | | | | | | | | | | - modified SQLCompiler to support rendering of bind parameters as literal inline strings for specific sections, if specified by the compiler subclass, using either literal_binds=True passed to process() or any visit method, or by setting to False the "binds_in_columns_clause" flag for SQL-92 compatible columns clauses.. The compiler subclass is responsible for implementing the literal quoting function which should make use of the DBAPI's native capabilities. - SQLCompiler now passes **kw to most process() methods (should be all, ideally) so that literal_binds is propagated. - added some rudimentary tests for mxodbc.
* - the execution sequence pulls all rowcount/last inserted IDMike Bayer2010-02-281-1/+5
| | | | | | | | info from the cursor before commit() is called on the DBAPI connection in an "autocommit" scenario. This helps mxodbc with rowcount and is probably a good idea overall. - cx_oracle wants list(), not tuple(), for empty execute. - cleaned up plain SQL param handling
* some ms/odbc fixesMike Bayer2010-02-281-2/+2
|
* further numeric fixesMike Bayer2010-02-271-3/+9
|
* working on pyodbc / mxodbcMike Bayer2010-02-271-34/+43
|
* - The assert_unicode flag is deprecated. SQLAlchemy will raiseMike Bayer2010-02-251-20/+0
| | | | | | a warning in all cases where it is asked to encode a non-unicode Python string, and will do nothing for DBAPIs that already accept Python unicode objects.
* Removed the text_as_varchar option in the mssql dialect. It wasn't being used.Michael Trier2010-02-231-1/+0
|
* long linesMike Bayer2010-02-231-1/+2
|
* - Added an optional C extension to speed up the sql layer byGaëtan de Menten2010-02-131-14/+3
| | | | | | | | | | | | | | | 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.
* - types.Binary is renamed to types.LargeBinary, it onlyMike Bayer2010-01-231-26/+6
| | | | | | | produces BLOB, BYTEA, or a similar "long binary" type. New base BINARY and VARBINARY types have been added to access these MySQL/MS-SQL specific types in an agnostic way [ticket:1664].
* reflect MSSQL cols that have descending markers [ticket:1629]Mike Bayer2010-01-161-1/+2
|
* - The Boolean type, when used on a backend that doesn'tMike Bayer2009-12-061-21/+1
| | | | | | | | | | have native boolean support, will generate a CHECK constraint "col IN (0, 1)" along with the int/smallint- based column type. This can be switched off if desired with create_constraint=False. Note that MySQL has no native boolean *or* CHECK constraint support so this feature isn't available on that platform. [ticket:1589]
* - changed a few isinstance(value, Decimal) to "is not None", where appropriateGaëtan de Menten2009-11-281-1/+7
| | | | - fixed result processor for Numeric(asdecimal=False) on MSSQL.
* - pg8000 + postgresql dialects now check for float/numeric returnMike Bayer2009-11-151-4/+4
| | | | | | | | | | 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..
* - dialect.get_default_schema_name(connection) is nowMike Bayer2009-11-031-3/+0
| | | | | public via dialect.default_schema_name. [ticket:1571]
* Removed references to sequence in MSSQLMichael Trier2009-10-221-1/+4
| | | | | | | Implicit identities in mssql work the same as implicit sequences on any other dialects. Explicit sequences are enabled through the use of "default=Sequence()". See the MSSQL dialect documentation for more information.
* Corrected problem with a Trusted Connection under MSSQL 2008 native driver.Michael Trier2009-10-051-1/+1
|
* avoid __nonzero__ on ClauseElementsPhilip Jenvey2009-10-011-11/+12
|
* merge from branches/clauseelement-nonzeroPhilip Jenvey2009-09-241-1/+1
| | | | | | adds a __nonzero__ to _BinaryExpression to avoid faulty comparisons during hash collisions (which only occur on Jython) fixes #1547
* close cursors: mostly fetchone -> firstPhilip Jenvey2009-09-111-4/+2
|
* - simplify MySQLIdentifierPreparer into standard pattern,Mike Bayer2009-08-101-1/+0
| | | | | | | thus allowing easy subclassing - move % sign logic for MySQLIdentifierPreparer into MySQLdb dialect - paramterize the escape/unescape quote char in IdentifierPreparer - cut out MySQLTableDefinitionParser cruft
* python3k fixesMike Bayer2009-08-091-2/+2
|
* clean up the way we detect MSSQL's form of RETURNINGMike Bayer2009-08-081-1/+2
|
* merge 0.6 series to trunk.Mike Bayer2009-08-061-0/+1448
View Lorry Controller Status