summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy/dialects/sybase
Commit message (Collapse)AuthorAgeFilesLines
...
* -whitespace bonanza, contdMike Bayer2012-07-282-4/+4
|
* trailing whitespace bonanzaMike Bayer2012-07-281-8/+8
|
* - pass kw through hereMike Bayer2012-06-251-1/+1
|
* - upgrade DBAPI index to have links to all dialect toplevel pagesMike Bayer2012-05-261-2/+6
| | | | - add line for google DBAPI
* typoes in lib/sqlalchemy/dialectsDiana Clarke2012-03-171-4/+4
|
* - [feature] Dialect-specific compilers now raiseMike Bayer2012-01-281-1/+1
| | | | | | | | CompileException for all type/statement compilation issues, instead of InvalidRequestError or ArgumentError. The DDL for CREATE TABLE will re-raise CompileExceptions to include table/column information for the problematic column. [ticket:2361]
* happy new yearMike Bayer2012-01-043-3/+3
|
* - 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-023-24/+24
|
* - clean up copyright, update for 2011, stamp every file withMike Bayer2011-01-025-3/+21
| | | | | 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.
* - move LIMIT/OFFSET rendering to be as bind parameters, for all backendsMike Bayer2010-08-291-0/+2
| | | | | | | | | | which support it. This includes SQLite, MySQL, Postgresql, Firebird, Oracle (already used binds with ROW NUMBER OVER), MSSQL (when ROW NUMBER is used, not TOP). Not included are Informix, Sybase, MaxDB, Access [ticket:805] - LIMIT/OFFSET parameters need to stay as literals within SQL constructs. This because they may not be renderable as binds on some backends.
* - Changed the scheme used to generate truncatedMike Bayer2010-07-211-1/+1
| | | | | | | | | | | | "auto" index names when using the "index=True" flag on Column. The truncation only takes place with the auto-generated name, not one that is user-defined (an error would be raised instead), and the truncation scheme itself is now based on a fragment of an md5 hash of the identifier name, so that multiple indexes on columns with similar names still have unique names. [ticket:1855]
* 78 chars for sybaseMike Bayer2010-07-063-21/+37
|
* this is a rewrite from the old sybase module with almost nothingMike Bayer2010-03-271-5/+6
| | | | remaining from the original, setting primary copyright
* - Added with_hint() method to Query() construct. This callsMike Bayer2010-03-271-0/+3
| | | | | | | | | | directly down to select().with_hint() and also accepts entities as well as tables and aliases. See with_hint() in the SQL section below. [ticket:921] - Added with_hint() method to select() construct. Specify a table/alias, hint text, and optional dialect name, and "hints" will be rendered in the appropriate place in the statement. Works for Oracle, Sybase, MySQL. [ticket:921]
* 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.
* removed all dialect table_names() methods and standardizedMike Bayer2010-03-191-3/+0
| | | | on get_table_names(). [ticket:1739]
* 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.
* - normalize sybase version numbersMike Bayer2010-03-182-1/+11
| | | | - sybase has 255 identifier length on 15, 30 earlier
* some weird numerictype coming back from pysybase, run through float()Mike Bayer2010-03-181-0/+13
|
* turning the decimals to floats allows the E notation to work with ↵Mike Bayer2010-03-182-4/+28
| | | | sybase+pyodbc for small E notations
* working through syb capabilitiesMike Bayer2010-03-171-3/+0
|
* - pyodbc can do *some* unicode with sybase, python-sybase not at all.Mike Bayer2010-03-174-6/+46
| | | | | 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-172-24/+15
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - 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.
* | - basic sybase+pyodbc support. in particular this will impact freetds ↵Mike Bayer2010-03-174-15/+42
|/ | | | detection for MS-SQL as well.
* - name all the "sub" dialect components <DB><component>_<dialectname>, ↵Mike Bayer2010-03-142-4/+4
| | | | [ticket:1738]
* - many incantations to get the tests to run reasonablyMike Bayer2010-03-142-7/+46
| | | | | - executemany() for some reason uses some tiny buffer, overriding it - we need to use the IDENTITY_INSERT thing
* - initial working version of sybase, with modifications to the transactionalMike Bayer2010-03-146-276/+241
| | | | | | | | | | 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
* - Added an optional C extension to speed up the sql layer byGaëtan de Menten2010-02-131-18/+1
| | | | | | | | | | | | | | | 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-6/+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].
* seriously, this is not 0.6 code !Mike Bayer2009-12-061-1/+3
|
* add a warning for unported dialects. considered a full blown ↵Mike Bayer2009-12-061-0/+2
| | | | NotImplementedError but will see if this gets the message across
* - pg8000 + postgresql dialects now check for float/numeric returnMike Bayer2009-11-151-1/+1
| | | | | | | | | | 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-2/+3
| | | | | public via dialect.default_schema_name. [ticket:1571]
* close cursors: mostly fetchone -> firstPhilip Jenvey2009-09-111-4/+1
|
* merge 0.6 series to trunk.Mike Bayer2009-08-065-0/+534