Open Source RDBMS - Seamless, Scalable, Stable and Free

한국어 | Login |Register

CUBRID Python Driver 9.1.0 release note

Changed and Enhanced Features:

  1. Support set as parameter of excute
  2. Link static lib of cci, so python'driver is not depend on cubrid
  3. The driver is support cubrid version 8.4.1,8.4.3,8.4.4 and 9.1.0.

New Feature:

  • APIS-370 - CUBRID python driver should support SET types (LIST/SET/MULTISET) in prepared statements
  • APIS-371 - CUBRID python driver should coerse values given with e- or e+ to NUMERIC

Fixed bugs:

Known bugs:


  • APIS-270 - Python Fetchone get bit varying data is not correct
  • APIS-520 - PythonError information is not correct
  • APIS-92 - Python Fetchone get bit varying data is not correct
  • APIS-489 - python The descriptions of Collection Datetypes are different in 32 bit linux and 64 bit linux
  • APIS-274 - GET TRANSACTION ISOLATION LEVEL returns None object

Fixed bugs:

  • APIS-522: Fix the date_format error in django_cubrid.
  • APIS-523: Fix the 'LIMIT' format error in django_cubrid.

Django backend Features:

In this version, the django support is developed. Django_cubrid is the django backend for CUBRID Database.

  1. Overview
  2. Django_cubrid is the official Django backend for CUBRID Database. When using Django web framework with CUBRID database, the django_cubrid backend should be used.
  3. Prerequisites
  4. * Python

    Being a Python Web framework, Django requires Python. It works with any Python version from 2.5 to 2.7 (due to backwards incompatibilities in Python 3.0, Django does not currently work with Python 3.0).
    So, when using django_cubrid, the Python version should be from 2.5 to 2.7.

    * Django

    Now supports Django-1.4 and Django-1.5, not support Django-1.3.
  5. Known issues
  6. * The Django sqlflush command maybe failed because of the foreign constraints between database tables.

    * After using the Django loaddata command, the insert SQL manipulation in the application maybe failed, becuse of the auto_increment field.

    * Perhaps you may encounter the below warning:
    RuntimeWarning: DateTimeField received a naive datetime (2013-01-15 06:38:37.463000) while time zone support is active.
    The reason is that CUBRID dosen't support timezone. You can set "USE_TZ" to False in to avoid this warning.

  7. Refer to How to use Django with CUBRID for more infomation.

Changed and Enhanced Features:

  1. Support designated charset in the key-value arguments of connect()
  2. Add the mult-byte character support for the data in CUBRID
  3. Support bind NULL value to sql statement
  4. Support bind unicode string to sql statement
  5. Support bind integer to sql statement
  6. Add the iteration feature for cursor object.
  7. Update the samples
  8. Update the README file
  9. Move the unit test cases into tests/
  10. Enable cci_connect_with_url_ex(), cci_escape_string() in Windows platfrom

Fixed bugs:

  • APIS-423: Access the major version and minor version from sys.version_info by indexing.
  • APIS-426: The unicode keyword isn't supported in cursor() when using Python-3.x
  • APIS-419: Add break in the switch in the _cubrid_ConnectionObject_schema_to_pyvalue().
  • APIS-428: Change the to fix the pip installation failure..
  • APIS-433: Fix the memory leak when using insert_id function in Windows platform
  • APIS-444: Fix Py_ssize_t undefined problem in Python-2.4. This bug causes fail to build in Python 2.4.
  • APIS-403: Improve the invoking of cci_disconnect().
  • APIS-419: Add break in the switch in the _cubrid_ConnectionObject_schema_to_pyvalue().
  • APIS-471: Check the parameter of set_autocommit() is or not a bool.
  • APIS-473: Remove as_sql() and create_test_db() in django_cubrid to support Django-1.5.
  • APIS-482: Fix the bug when reuse a closed connection to create a cursor.
comments powered by Disqus
Page info
viewed 2122 times
translations en
posted 4 years ago by
updated 4 years ago by
View revisions
Share this article