summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy/dialects/access/base.py
Commit message (Collapse)AuthorAgeFilesLines
* - [feature] the MS Access dialect has beenMike Bayer2012-09-301-444/+0
| | | | | | | | | | moved to its own project on Bitbucket, taking advantage of the new SQLAlchemy dialect compliance suite. The dialect is still in very rough shape and probably not ready for general use yet, however it does have *extremely* rudimental functionality now.
* - [feature] To complement [ticket:2547], typesMike Bayer2012-08-171-7/+0
| | | | | | | | | | | | | | | | can now provide "bind expressions" and "column expressions" which allow compile-time injection of SQL expressions into statements on a per-column or per-bind level. This is to suit the use case of a type which needs to augment bind- and result- behavior at the SQL level, as opposed to in the Python level. Allows for schemes like transparent encryption/ decryption, usage of Postgis functions, etc. [ticket:1534] - update postgis example fully. - still need to repair the result map propagation here to be transparent for cases like "labeled column".
* -whitespace bonanza, contdMike Bayer2012-07-281-6/+6
|
* - upgrade DBAPI index to have links to all dialect toplevel pagesMike Bayer2012-05-261-2/+3
| | | | - add line for google DBAPI
* - move maxdb notes from wiki to the maxdb moduleMike Bayer2011-01-181-2/+2
| | | | - move exception docs down to the lower portion of core/orm
* - whitespace removal bonanzaMike Bayer2011-01-021-2/+2
|
* - clean up copyright, update for 2011, stamp every file withMike Bayer2011-01-021-1/+2
| | | | | a consistent tag - AUTHORS file
* - an approach I like better, remove most adapt() methods and use a genericMike Bayer2010-12-151-5/+0
| | | | | copier - mssql reflection fix, but this will come in again from the tip merge
* - 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]
* - idle 78-char adjustmentsMike Bayer2010-07-031-29/+65
|
* - Fixed incorrect signature in do_execute() for firebird, access, errorMike Bayer2010-06-091-1/+1
| | | | introduced in 0.6.1. [ticket:1823]
* removed all dialect table_names() methods and standardizedMike Bayer2010-03-191-2/+3
| | | | on get_table_names(). [ticket:1739]
* - added pyodbc for sybase driver.Mike Bayer2010-03-171-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | - 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).
* - Added an optional C extension to speed up the sql layer byGaëtan de Menten2010-02-131-37/+8
| | | | | | | | | | | | | | | 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-2/+2
| | | | | | | 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-0/+2
|
* 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-3/+3
| | | | | | | | | | 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..
* merge 0.6 series to trunk.Mike Bayer2009-08-061-0/+442
View Lorry Controller Status