summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy/cextension
Commit message (Collapse)AuthorAgeFilesLines
* - copyright 2015Mike Bayer2015-03-103-3/+3
|
* - rework Oracle to no longer do its own unicode conversion; this has been ↵Mike Bayer2014-01-171-0/+41
| | | | | | | | | | | observed to be very slow. this now has the effect of producing "conditional" unicode conversion for the Oracle backend, as it still returns NVARCHAR etc. as unicode [ticket:2911] - add new "conditional" functionality to unicode processors; the C-level function now uses PyUnicode_Check() as a fast alternative to the isinstance() check in Python
* Use PyMODINIT_FUNCpr/55cgohlke2014-01-081-1/+1
|
* Use PyMODINIT_FUNCcgohlke2014-01-081-1/+1
|
* Use PyMODINIT_FUNCcgohlke2014-01-081-1/+1
|
* - happy new yearMike Bayer2014-01-053-3/+3
|
* - The C extensions are ported to Python 3 and will build underMike Bayer2013-07-263-45/+352
| | | | any supported CPython 2 or 3 environment. [ticket:2161]
* happy new year (see #2645)Diana Clarke2013-01-013-3/+3
|
* fix some warningsMike Bayer2012-08-281-3/+11
|
* - [bug] Fixed cextension bug whereby theMike Bayer2012-08-221-3/+10
| | | | | | | | | | | | | | | | | | | "ambiguous column error" would fail to function properly if the given index were a Column object and not a string. Note there are still some column-targeting issues here which are fixed in 0.8. [ticket:2553] - find more cases where column targeting is being inaccurate, add more information to result_map to better differentiate "ambiguous" results from "present" or "not present". In particular, result_map is sensitive to dupes, even though no error is raised; the conflicting columns are added to the "obj" member of the tuple so that the two are both directly accessible in the result proxy - handwringing over the damn "name fallback" thing in results. can't really make it perfect yet - fix up oracle returning clause. not sure why its guarding against labels, remove that for now and see what the bot says.
* - add new C extension "utils", so far includes distill_paramsMike Bayer2012-08-073-0/+191
| | | | | - repair test_processors which wasn't hitting the python functions - add another suite to test_processors that does distill_params
* - break out engine/base.py into base, interfaces, result, util.Mike Bayer2012-08-071-7/+7
| | | | - remove deprecated 0.7 engine methods
* - [bug] Fixed memory leak in C version ofMike Bayer2012-06-011-6/+18
| | | | | | | | result proxy whereby DBAPIs which don't deliver pure Python tuples for result rows would fail to decrement refcounts correctly. The most prominently affected DBAPI is pyodbc. [ticket:2489]
* - [bug] Fixed issue whereby attribute-basedMike Bayer2012-03-141-1/+10
| | | | | | | | column access on a row would raise AttributeError with non-C version, NoSuchColumnError with C version. Now raises AttributeError in both cases. [ticket:2398]
* - [bug] Fixed bug in C extensions wherebyMike Bayer2012-03-131-15/+10
| | | | | | | | string format would not be applied to a Numeric value returned as integer; this affected primarily SQLite which does not maintain numeric scale settings. [ticket:2432]
* - [bug] Fixed memory leak in core which wouldMike Bayer2012-03-101-0/+6
| | | | | | | occur when C extensions were used with particular types of result fetches, in particular when orm query.count() were called. [ticket:2427]
* o null check PyObject_Repr resultsPhilip Jenvey2012-01-232-7/+20
| | | | o limit size of strings passed to PyErr_Format
* - [bug] Fixed bug whereby a table-bound ColumnMike Bayer2012-01-221-1/+1
| | | | | | | | | | | object named "<a>_<b>" which matched a column labeled as "<tablename>_<colname>" could match inappropriately when targeting in a result set row. [ticket:2377] - requires that we change the tuple format in RowProxy. Makes an improvement to the cases tested against an unpickled RowProxy as well though doesn't solve the problem there entirely.
* - [bug] Improved error messages when a non-stringMike Bayer2012-01-221-6/+45
| | | | | | | | | or invalid string is passed to any of the date/time processors used by SQLite, including C and Python versions. [ticket:2382] - changed the import model of processors.py so that we can get at the pure python versions and C versions simultaneously in tests.
* - Added some defs to the resultproxy.c extension so thatMike Bayer2011-01-301-0/+2
| | | | | the extension compiles and runs on Python 2.4. [ticket:2023]
* fixed a small potential memory leak in UnicodeResultProcessor (for some weirdGaëtan de Menten2010-11-272-7/+15
| | | | | reason, it didn't actually leak in my tests) by providing a dealloc method to the type, and added a test to ensure it stays that way. Closes #1981.
* Fix memory leaks in the cprocessors DecimalResultProcessor, including tests. ↵Taavi Burns2010-11-191-1/+10
| | | | [ticket:1978]
* - Implemented sequence check capability for the CMike Bayer2010-11-091-1/+7
| | | | | | version of RowProxy, as well as 2.7 style "collections.Sequence" registration for RowProxy. [ticket:1871]
* take2 on #1781.Gaëtan de Menten2010-04-271-1/+2
|
* Hopefully fix C extension on python2.4 (ticket #1781), however I can't test itGaëtan de Menten2010-04-262-0/+13
| | | | currently.
* - enginesGaëtan de Menten2010-04-111-5/+9
| | | | | - The C extension now also works with DBAPIs which use custom sequences as row (and not only tuples). [ticket:1757]
* ... also when changing the row dynamicallyGaëtan de Menten2010-04-021-1/+1
|
* - made the C version of RowProxy accept any sequence for the row, instead ofGaëtan de Menten2010-04-021-17/+16
| | | | only tuples
* support scale argument for the C implementation of the decimal processorGaëtan de Menten2010-02-281-5/+14
|
* fix typoGaëtan de Menten2010-02-241-1/+1
|
* - fix C version of rowproxy pickling so that it pickles to the same formatGaëtan de Menten2010-02-141-2/+2
| | | | | as the Python version. - changelog my earlier processor optimization work
* fixed a huge bug in the C version of the unicode processorGaëtan de Menten2010-02-141-1/+1
|
* - Added an optional C extension to speed up the sql layer byGaëtan de Menten2010-02-132-0/+970
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.
View Lorry Controller Status