Skip to content
Commits on Feb 9, 2012
  1. @avidal
Commits on Feb 7, 2012
  1. @avidal
Commits on Feb 3, 2012
  1. @avidal

    Make it backwards compatible.

    avidal committed Feb 3, 2012
  2. @avidal
  3. @avidal

    Support for django 1.4 alpha.

    * Added _DJANGO_VERSION to the DatabaseWrapper so it'd be available in the
      various Database* objects
    * Check if _DJANGO_VERSION >= 14 when calling DatabaseOperations superclass
      init method to be compatible with django 1.4
    * Guard against settings.DATABASE_OPTIONS not existing
    avidal committed Feb 2, 2012
  4. @avidal

    Add gitignore file.

    avidal committed Feb 3, 2012
Commits on Apr 17, 2011
  1. Fixed issue #95, thanks tellnoel.

    vcc@163.com committed Apr 17, 2011
  2. Fixed issue #101, thanks redjohn367.

    vcc@163.com committed Apr 17, 2011
  3. Fixed issue #92 Port number incorrect for dsnless connections, thanks…

    … shai%platonix.com@gtempaccount.com.
    vcc@163.com committed Apr 17, 2011
  4. Fixed issue #81, sql_server_ver in multi-db-engine environment, thank…

    …s hgeerts.
    vcc@163.com committed Apr 17, 2011
Commits on Mar 25, 2011
  1. fix missing colon, sorry.

    vcc@163.com committed Mar 25, 2011
Commits on Mar 24, 2011
  1. Update for Django 1.3 release.

    vcc@163.com committed Mar 24, 2011
Commits on Jul 22, 2010
  1. Fixed issue #75, thanks SheepNine.

    vcc@163.com committed Jul 22, 2010
Commits on Jun 7, 2010
  1. Fixed Issue #83, move convert_values to DatabaseOperations class, tha…

    …nks gokhan.ipek.
    vcc@163.com committed Jun 7, 2010
Commits on Apr 30, 2010
  1. update sql_flush for support SQL Server 2008.

    vcc@163.com committed Apr 30, 2010
  2. Fix issue #73, thanks amagee and djfische.

    vcc@163.com committed Apr 30, 2010
  3. remove extra_where follow django trunk.

    vcc@163.com committed Apr 30, 2010
  4. workaround for Issue 79#

    vcc@163.com committed Apr 30, 2010
Commits on Jan 27, 2010
  1. Fixed Issue 72, thanks jordanthecoder.

    vcc@163.com committed Jan 27, 2010
Commits on Jan 24, 2010
  1. Fixed #70 -- add iter to CursorWrapper, thanks amagee.

    vcc@163.com committed Jan 24, 2010
Commits on Jan 18, 2010
  1. Add new pyodbc 2.1.5 unicode_results support, thanks jacques.beaurain…

    … for patch.
    vcc@163.com committed Jan 18, 2010
Commits on Jan 12, 2010
  1. Fixed for Django 1.2 alpha 1, from django trunk revision 11952 Added …

    …multiple database support.
    vcc@163.com committed Jan 12, 2010
Commits on Aug 11, 2009
  1. add setup.py.

    vcc@163.com committed Aug 11, 2009
Commits on Jul 26, 2009
Commits on May 11, 2009
  1. Fixed return type of our query class resolve_columns method emulating…

    … Django changeset 10742. This solves one test failure. Thanks Jirka Vejrazka.
    cramm0 committed May 11, 2009
Commits on Apr 21, 2009
  1. Fixed issue 49, special-case dtime fields with value set to midnight …

    …when handling SQL Server date/time compatibility.
    cramm0 committed Apr 21, 2009
Commits on Apr 14, 2009
  1. add order_by('?') limit/offset for sql server 2005.

    vcc@163.com committed Apr 14, 2009
Commits on Mar 30, 2009
Commits on Mar 27, 2009
  1. fixed resolve_columns for extra_select, add value_to_db_decimal, date…

    … trunc for day use ISO yyyymmdd format.
    vcc@163.com committed Mar 27, 2009
Commits on Mar 13, 2009
  1. Removed extra debug print from tests.

    cramm0 committed Mar 13, 2009
Commits on Mar 11, 2009
  1. Follow-up to r155: Migrated DATABASE_ODBC_DRIVER, DATABASE_ODBC_DSN a…

    …nd DATABASE_ODBC_EXTRA_PARAMS settings to DATABASE_OPTIONS.
    
    This is a backward-incompatible change for setups that were using al least one
    of these three settings.
    
    The equivalente DATABASE_OPTIONS keys are 'driver, 'dsn' and 'extra_params'
    respectively.
    
    The DATABASE_COLLATION setting will be subject to the same migration
    (to DATABASE_OPTIONS['collation']) soon (it needs some additional
    re-factoring), for now it raises a DeprecationWarning.
    cramm0 committed Mar 11, 2009
Something went wrong with that request. Please try again.