Using python 3.2 with django 1.5.1, I am getting DatabseError is not indexable in firebird/base.py.

Affected lines are:
156: if e[0] in self.codes_for_integrityerror:
162: if e[0] in self.codes_for_integrityerror:
182: return tuple([e[0], '%s -- %s' % (e[1], q % tuple(p))])

changing to the following fixes the issue:
156: if e.args[0] in self.codes_for_integrityerror:
162: if e.args[0] in self.codes_for_integrityerror:
182: return tuple([e.args[0], '%s -- %s' % (e.args[1], q % tuple(p))])

Hello maironaina I'm working with fdb in a project but I need implement database migration you know if a can do migration with a firebird database in django?

Implement support for new schema migration in django 1.7

Whe i follow Blog Posts in the admin area
http://mariuz.android-dev.ro/admin/blog/blogpost/

of Mezzanine 3.0.x and django 1.6.2

I get this error

Exception Type:NotImplementedError
Exception Location:/usr/local/lib/python2.7/dist-packages/django/db/backends/init.py
in datetime_trunc_sql, line 764

seems to be in

connection.ops.datetime_trunc_sql(self.lookup_type, col, self.tzname)
/usr/local/lib/python2.7/dist-packages/django/db/models/sql/datastructures.py

ps: the previous error was solved 👍

Add this to README
https://caniusepython3.com/project/django-firebird

Hello, do you know what's happening? and as I do to fix it

(sigma)cfpp@cfpp-notebook:~/sigma/src$ manage inspectdb > models.py
Traceback (most recent call last):
File "/home/cfpp/sigma/src/manage.py", line 10, in
execute_from_command_line(sys.argv)
File "/home/cfpp/sigma/local/lib/python2.7/site-packages/django/core/management/init.py", line 399, in execute_from_command_line
utility.execute()
File "/home/cfpp/sigma/local/lib/python2.7/site-packages/django/core/management/init.py", line 392, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/home/cfpp/sigma/local/lib/python2.7/site-packages/django/core/management/base.py", line 242, in run_from_argv
self.execute(_args, *_options.dict)
File "/home/cfpp/sigma/local/lib/python2.7/site-packages/django/core/management/base.py", line 285, in execute
output = self.handle(_args, *_options)
File "/home/cfpp/sigma/local/lib/python2.7/site-packages/django/core/management/base.py", line 415, in handle
return self.handle_noargs(**options)
File "/home/cfpp/sigma/local/lib/python2.7/site-packages/django/core/management/commands/inspectdb.py", line 27, in handle_noargs
for line in self.handle_inspection(options):
File "/home/cfpp/sigma/local/lib/python2.7/site-packages/django/core/management/commands/inspectdb.py", line 40, in handle_inspection
cursor = connection.cursor()
File "/home/cfpp/sigma/local/lib/python2.7/site-packages/django/db/backends/init.py", line 160, in cursor
cursor = self.make_debug_cursor(self._cursor())
File "/home/cfpp/sigma/local/lib/python2.7/site-packages/django/db/backends/init.py", line 132, in _cursor
self.ensure_connection()
File "/home/cfpp/sigma/local/lib/python2.7/site-packages/django/db/backends/init.py", line 127, in ensure_connection
self.connect()
File "/home/cfpp/sigma/local/lib/python2.7/site-packages/django/db/utils.py", line 99, in exit
six.reraise(dj_exc_type, dj_exc_value, traceback)
File "/home/cfpp/sigma/local/lib/python2.7/site-packages/django/db/backends/init.py", line 127, in ensure_connection
self.connect()
File "/home/cfpp/sigma/local/lib/python2.7/site-packages/django/db/backends/init.py", line 115, in connect
self.connection = self.get_new_connection(conn_params)
File "/home/cfpp/sigma/local/lib/python2.7/site-packages/firebird/base.py", line 126, in get_new_connection
return Database.connect(**conn_params)
File "/home/cfpp/sigma/local/lib/python2.7/site-packages/fdb/fbcore.py", line 693, in connect
"Error while connecting to database:")
django.db.utils.DatabaseError: ('Error while connecting to database:\n- SQLCODE: -922\n- file /var/lib/firebird/2.5/data/sigma.fdb is not a valid database', -922, 335544323)

Here what i have

Django==1.8
django-firebird===1.6.1.final.0
fdb==1.4.4

Query causes an error:

'firebird' isn't an available database backend.
Try using 'django.db.backends.XXX', where XXX is one of:
    u'base', u'mysql', u'oracle', u'postgresql_psycopg2', u'sqlite3'
Error was: cannot import name BaseDatabaseOperations

date_interval_sql is not implemented

In the FirebirdCursorWrapper class, on execute and executemany there is a lost of error info on exception.
The error_info method changes the standard on exception format data, and makes impossible the introspection information.
We need to have, error message, sqlcode and error code. SQL text and params is a plus.

When use inspected, only create this:

class VendaPedidoItens(models.Model):
class Meta:
db_table = u'venda_pedido_itens'

doesn`t create the Fields

The methods add_field, _alter_field has been changed.

Ej: new_field.rel to new_field.remote_field

The new BinaryField data type added in django 1.6 is not supported by introspection.

BigIntegerField data type is not supported in introspection.

FDB (version 1.4.7) raise exception in two different ways, It raise an exception using "exception_from_status" function or using a standard exception class, for example ProgrammingError.

Depends on which approach fdb uses, the exception information changes. If it uses exception_from_status, the exception include: error message, sqlcode and error_code, If not, using ProgrammingError just the error message is included.

In the FirebirdCursorWrapper class the error_info method try to customize the exception info and make this more homogeneous (including sql statement and params if any), but it fails if exception_from_status is not used.

For example:

File "/home/chase/.virtualenvs/.../local/lib/python2.7/site-packages/firebird/base.py", line 241, in error_info
return tuple([e.args[0], e.args[1], e.args[2], {'sql': sql_text, 'params': p}])

IndexError: tuple index out of range

e.args[2] doesn't exists if ProgrammingError is raised

e.args[0] = Exception message
e.args[1] = sql_code
e.args[2] = error_code

In django 1.7, in DatabaseCreation, now we have a data_type_check_constraints to separate checks constraints of data type definition.

The ROLE param must be optional.
If ROLE is not specified in DATABASE setting a error is raised.

Hello everyone,

I'm trying to integrate a firebird legacy database with my postgres database using this amazing project, but, during the tests, I've got the error AttributeError: 'DatabaseWrapper' object has no attribute 'Database'.

The model was mapped from an existing table:

class Equipment(models.Model):

    class Meta:
        managed = False
        db_table = '...'

    objects = EquipmentManager()

    id = models.IntegerField(db_column='...', primary_key=True)
    description = models.CharField(db_column='...', max_length=60)
    situation = models.CharField(db_column='...', max_length=1)


class EquipmentManager(models.Manager):

    def get_query_set(self):
        return super(EquipmentManager, self).get_query_set().filter(
            situation='A')

# This code raises the error
>>> for e in Equipment.objects.all(): print e.id, e.description

I tried with Meta.managed = True and custom Manager with same results.

I imagine that this error is hiding another one. What we can do about it?

Thanks.

Implement DatabaseOperations.sequence_reset_sql using ALTER SEQUENCE statement.

I discovered that django-firebird does not support the role, despite the fact that fdb supports them.

I tried to fix it.

https://gist.github.com/tbazadaykin/e6988c30f76e093cb902

pip install django-firebird
There are not firebird folder in ..../django/db/backends
Thanks
Regards

In Database Introspection the get_index method should return all index of a table not just primary or unique keys.
We need to fix this to better introspection support (useful in the new schema migration)

sorry i'm newbie, if I install with 'pip install djano-firebird' it works ok. but I think that doesn't install your latest version.

but if I tried to manual install with

git clone git://github.com/maxirobaina/django-firebird.git
cd django-firebird
sudo python setup.py install

I get this

Traceback (most recent call last):
File "setup.py", line 14, in <module>
version = __import__('firebird').get_version()
AttributeError: 'module' object has no attribute 'get_version'

is normal? or I'm doing things wrong.
I tried with a python2.7 or with a mkvirtualenv with python3.4

thanks in advance.

The flush command doesn't work. It fails when try to clear a table with Foreign key references.

Hi,

I am trying to use this driver with Python 3.3 but get syntax errors when I try to install it with pip.

Is it Python 3 compatible or do you have plans for a Python 3 version?

Regards

In previous django version < 1.8, get_relation method had the following implementation

Returns a dictionary of {field_index: (field_index_other_table, other_table)}
representing all relationships to the given table. Indexes are 0-based.

Now, it changes to

Returns a dictionary of {field_name: (field_name_other_table, other_table)}
representing all relationships to the given table.

So, database introspections test fails.

Update operations.py to support django 1.9

• Implement datetime_cast_date_sql
• Check implementation of year_lookup_bounds_for_date_field (May be no need anymore)
• Check implementation of year_lookup_bounds_for_datetime_field (year_lookup_bounds doesn't exists anymore?)
• value_to_db_... methods were replaced for adapt_..._value
  Ej: value_to_db_datetime now is adapt_datetimefield_value

Check more info at https://docs.djangoproject.com/es/1.9/releases/1.9/#database-backend-api

Make new DurationField works
https://docs.djangoproject.com/en/1.8/ref/models/fields/#durationfield
https://docs.djangoproject.com/es/1.9/releases/1.8/#new-data-types

When a models is deleted, related database objects used to support autoinc field aren't deleted (sequence and triggers)

New in Django 1.8.

Make new UUIDField works
https://docs.djangoproject.com/en/1.8/ref/models/fields/#uuidfield

Hi, i'm using win7, python 2.7, firebird 2.1.2, django 1.5.2, fdb 1.4, django-firebird 1.6.0 alpha, and I receive an error, DatabaseWrapper object has no attribute '_cursor'.
What i'm doing wrong? Thank's a lot!

This package doesn't support the new PEP 440 version specification, so PyPI upload fails. Fix it.

Related to issue #62

Have used Django in the past, but not recently - thanks for undertaking this project! It is something we Firebird users are really excited about. Or should be, if we haven't heard about it yet.

Where is the appropriate place to watch for questions and answers about this nice project? Am I in the right place?

DatabaseOperations change convert_values method by get_db_converters and convert_{fieldtype}_value related methods.

For example: convert_booleanfield_value

def convert_booleanfield_value(self, value, expression, connection, context):
        if value in (0, 1):
            value = bool(value)
        return value

The execute method of FirebirdCursorWrapper doesn't catch violation on foreign key constraints (error code -530) as integrity error

I'm trying to run the lib on flynn.io (a alternative to heroku) that use buildpacks.

I'm using multi buildpack with .buildpacks like:

https://github.com/ddollar/heroku-buildpack-apt
https://github.com/heroku/heroku-buildpack-python

The heroku-buildpack-apt is used to install libfbclient2. The buildpack install it at /app/.apt/usr/lib/x86_64-linux-gnu, but after get the error, I found that the fdb python module doesn't look at LD_LIBRARY_PATH where the ".apt" folder is inserted.

How can I point to django-firebird an additional location (.apt folder, in case) to avoid the error?

The core database backends return views in introspection, get_table_list method. Make firebird
consistent with that.

See at:
https://code.djangoproject.com/ticket/6730
https://code.djangoproject.com/ticket/18782
https://code.djangoproject.com/ticket/21272

Hi!
I'm using the following setup (all installed with pip install):
Django (1.7.11)
django-firebird (1.7)
fdb (1.6)

I connect to firebird database with gui razorsql and I connect successfully with this line:
jdbc:firebirdsql://test.testdomain.com:18006/DBtest (I changed a bit domain and port, and of course there are also user/password)

I have clean django project created by django 1.7.11 with this modification:

DATABASES = {
    'default': {
        'ENGINE' : 'firebird',
        'NAME' : 'DBtest', # Path to database or db alias
        'USER' : 'user',           # Your db user
        'PASSWORD' : '*****',    # db user password
        'HOST' : 'test.testdomain.com',        # Your host machine
        'PORT' : '18006',             # If is empty, use default 3050
    }
}

(of course with right user and password)

When I launch server (python manage.py runserver) nothing happens.

python manage.py runserver
Performing system checks...

System check identified no issues (0 silenced).

when I launch it with deafult sqlite generated settings:

DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.sqlite3',
        'NAME': os.path.join(BASE_DIR, 'db.sqlite3'),
    }
}

default launching happens:

python manage.py runserver
Performing system checks...

System check identified no issues (0 silenced).

You have unapplied migrations; your app may not work properly until they are applied.
Run 'python manage.py migrate' to apply them.

April 20, 2016 - 13:55:50
Django version 1.7.11, using settings 'demofb.settings'
Starting development server at http://127.0.0.1:8000/
Quit the server with CONTROL-C.

So smth is wrong with firebird database setup. But what? Maybe I should use different combination of versions?

If a object with a TimeFiled attempt to strore a python time object with microseconds greater than 6 digit it fails.
In Firebird only 4 digits are allowed to microseconds.

Review implementation of DatabaseOperations.value_to_db_time

Hi There,
While testing with firebird 3 - suppose alter table etc. should be used instead...
UPDATE operation is not allowed for system table RDB$RELATION_FIELDS
pls let me know if more info is required - see below
Many thanks,
dvt

$ python3 manage.py migrate
Operations to perform:
Apply all migrations: admin, auth, contenttypes, sessions
Running migrations:
Applying contenttypes.0001_initial... OK
Applying auth.0001_initial... OK
Applying admin.0001_initial... OK
Applying admin.0002_logentry_remove_auto_add... OK
Applying contenttypes.0002_remove_content_type_name...Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 64, in execute
return self.cursor.execute(sql, params)
File "/usr/local/lib/python3.5/dist-packages/django_firebird-1.9a0-py3.5.egg/firebird/base.py", line 236, in execute
return self.cursor.execute(q, params)
File "/usr/local/lib/python3.5/dist-packages/fdb/fbcore.py", line 3576, in execute
self._ps._execute(parameters)
File "/usr/local/lib/python3.5/dist-packages/fdb/fbcore.py", line 3291, in _execute
"Error while executing SQL statement:")
fdb.fbcore.DatabaseError: ('Error while executing SQL statement:\n- SQLCODE: -902\n- UPDATE operation is not allowed for system table RDB$RELATION_FIELDS', -902, 335545030)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "manage.py", line 22, in
execute_from_command_line(sys.argv)
File "/usr/lib/python3/dist-packages/django/core/management/init.py", line 367, in execute_from_command_line
utility.execute()
File "/usr/lib/python3/dist-packages/django/core/management/init.py", line 359, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 294, in run_from_argv
self.execute(*args, **cmd_options)
File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 345, in execute
output = self.handle(*args, **options)
File "/usr/lib/python3/dist-packages/django/core/management/commands/migrate.py", line 204, in handle
fake_initial=fake_initial,
File "/usr/lib/python3/dist-packages/django/db/migrations/executor.py", line 115, in migrate
state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
File "/usr/lib/python3/dist-packages/django/db/migrations/executor.py", line 145, in _migrate_all_forwards
state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
File "/usr/lib/python3/dist-packages/django/db/migrations/executor.py", line 244, in apply_migration
state = migration.apply(state, schema_editor)
File "/usr/lib/python3/dist-packages/django/db/migrations/migration.py", line 129, in apply
operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
File "/usr/lib/python3/dist-packages/django/db/migrations/operations/fields.py", line 204, in database_forwards
schema_editor.alter_field(from_model, from_field, to_field)
File "/usr/lib/python3/dist-packages/django/db/backends/base/schema.py", line 495, in alter_field
old_db_params, new_db_params, strict)
File "/usr/local/lib/python3.5/dist-packages/django_firebird-1.9a0-py3.5.egg/firebird/schema.py", line 262, in _alter_field
self.execute(sql, params)
File "/usr/local/lib/python3.5/dist-packages/django_firebird-1.9a0-py3.5.egg/firebird/schema.py", line 404, in execute
cursor.execute(sql, params)
File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 79, in execute
return super(CursorDebugWrapper, self).execute(sql, params)
File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 64, in execute
return self.cursor.execute(sql, params)
File "/usr/lib/python3/dist-packages/django/db/utils.py", line 94, in exit
six.reraise(dj_exc_type, dj_exc_value, traceback)
File "/usr/lib/python3/dist-packages/django/utils/six.py", line 685, in reraise
raise value.with_traceback(tb)
File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 64, in execute
return self.cursor.execute(sql, params)
File "/usr/local/lib/python3.5/dist-packages/django_firebird-1.9a0-py3.5.egg/firebird/base.py", line 236, in execute
return self.cursor.execute(q, params)
File "/usr/local/lib/python3.5/dist-packages/fdb/fbcore.py", line 3576, in execute
self._ps._execute(parameters)
File "/usr/local/lib/python3.5/dist-packages/fdb/fbcore.py", line 3291, in _execute
"Error while executing SQL statement:")
django.db.utils.DatabaseError: ('Error while executing SQL statement:\n- SQLCODE: -902\n- UPDATE operation is not allowed for system table RDB$RELATION_FIELDS', -902, 335545030)

(sigma)cfpp@cfpp-notebook:~/sigma/src$ manage inspectdb
Traceback (most recent call last):
File "/home/cfpp/sigma/src/manage.py", line 10, in
execute_from_command_line(sys.argv)
File "/home/cfpp/sigma/local/lib/python2.7/site-packages/django/core/management/init.py", line 399, in execute_from_command_line
utility.execute()
File "/home/cfpp/sigma/local/lib/python2.7/site-packages/django/core/management/init.py", line 392, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/home/cfpp/sigma/local/lib/python2.7/site-packages/django/core/management/base.py", line 242, in run_from_argv
self.execute(_args, *_options.dict)
File "/home/cfpp/sigma/local/lib/python2.7/site-packages/django/core/management/base.py", line 285, in execute
output = self.handle(_args, *_options)
File "/home/cfpp/sigma/local/lib/python2.7/site-packages/django/core/management/base.py", line 415, in handle
return self.handle_noargs(**options)
File "/home/cfpp/sigma/local/lib/python2.7/site-packages/django/core/management/commands/inspectdb.py", line 27, in handle_noargs
for line in self.handle_inspection(options):
File "/home/cfpp/sigma/local/lib/python2.7/site-packages/django/core/management/commands/inspectdb.py", line 40, in handle_inspection
cursor = connection.cursor()
File "/home/cfpp/sigma/local/lib/python2.7/site-packages/django/db/backends/init.py", line 160, in cursor
cursor = self.make_debug_cursor(self._cursor())
File "/home/cfpp/sigma/local/lib/python2.7/site-packages/django/db/backends/init.py", line 132, in _cursor
self.ensure_connection()
File "/home/cfpp/sigma/local/lib/python2.7/site-packages/django/db/backends/init.py", line 127, in ensure_connection
self.connect()
File "/home/cfpp/sigma/local/lib/python2.7/site-packages/django/db/backends/init.py", line 115, in connect
self.connection = self.get_new_connection(conn_params)
File "/home/cfpp/sigma/local/lib/python2.7/site-packages/firebird/base.py", line 126, in get_new_connection
return Database.connect(**conn_params)
File "/home/cfpp/sigma/local/lib/python2.7/site-packages/fdb/fbcore.py", line 645, in connect
load_api()
File "/home/cfpp/sigma/local/lib/python2.7/site-packages/fdb/fbcore.py", line 176, in load_api
setattr(sys.modules[name],'api',fbclient_API())
File "/home/cfpp/sigma/local/lib/python2.7/site-packages/fdb/ibase.py", line 1155, in init
self.isc_attach_database = fb_library.isc_attach_database
File "/usr/lib/python2.7/ctypes/init.py", line 378, in getattr
func = self.getitem(name)
File "/usr/lib/python2.7/ctypes/init.py", line 383, in getitem
func = self._FuncPtr((name_or_ordinal, self))
AttributeError: python: undefined symbol: isc_attach_database

./manage dbshell fails on Linux platforms
The command line, Interactive SQL, on Linux is "isql-fb"
Current version is using "isql"

The backend engine fails to introspect boolean fields type. It must be represented by SmallInt data type.

Implement the new introspected_boolean_field_type in DatabaseFeatures

ERROR: test_rename (schema.tests.SchemaTests)

Traceback (most recent call last):
File "/home/maxi/projects/django/django-firebird/forks/github/django-firebird/tests/test_main/schema/tests.py", line 393, in test_rename
strict=True,
File "/usr/local/lib/python2.7/dist-packages/django/db/backends/schema.py", line 470, in alter_field
self._alter_field(model, old_field, new_field, old_type, new_type, old_db_params, new_db_params, strict)
File "/usr/local/lib/python2.7/dist-packages/firebird/schema.py", line 138, in _alter_field
fragment, other_actions = self._alter_column_type_sql(model._meta.db_table, new_field.column, new_type)
TypeError: _alter_column_type_sql() takes exactly 5 arguments (4 given)

I've tried to use django-firebird with django 1.7 and 1.8 and it don't work. The support to new django releases are in the project roadmap?

Thanks.

When running a query with aggregate function an error is raised because is just including the primary key in group by clause.

Check feature allows_group_by_pk. It must be False

Evaluante replace plain sql schema introspection by fdb schema api.

http://pythonhosted.org//fdb/usage-guide.html#working-with-database-schema

Working with database schema
Description of database objects like tables, views, stored procedures, triggers or UDF functions that represent database schema is stored in set of system tables present in every database. Firebird users can query these tables to get information about these objects and their relations. But querying system tables is inconvenient, as it requires good knowledge how this information is structured and requires significant amount of Python code. Changes in system tables between Firebird versions further add to this complexity. Hence FDB provides set of classes (isolated in separate module fdb.schema) that transform information stored in system tables into set of Python objects that surface the vital information in meaningful way, and additionaly provide set of methods for most commonly used operations or checks.

Hello.

I'm trying to complete Django tutorial using a Firebird DB, on the following configuration: Windows 8.1, Python 2.7.6, Django 1.6.2. Fdb 1.4, django-firebird 1.5.3.final.0.

When I try "syncdb" I get the following error:

Creating tables ...
Traceback (most recent call last):
  File "C:\Users\amira_000\eclipse-wks\PythonProjects\StartProjectFDB\src\manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "C:\Users\amira_000\virtualenv\vePy27\lib\site-packages\django\core\management\__init__.py", line 399, in execute_from_command_line
    utility.execute()
  File "C:\Users\amira_000\virtualenv\vePy27\lib\site-packages\django\core\management\__init__.py", line 392, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "C:\Users\amira_000\virtualenv\vePy27\lib\site-packages\django\core\management\base.py", line 242, in run_from_argv
    self.execute(*args, **options.__dict__)
  File "C:\Users\amira_000\virtualenv\vePy27\lib\site-packages\django\core\management\base.py", line 285, in execute
    output = self.handle(*args, **options)
  File "C:\Users\amira_000\virtualenv\vePy27\lib\site-packages\django\core\management\base.py", line 415, in handle
    return self.handle_noargs(**options)
  File "C:\Users\amira_000\virtualenv\vePy27\lib\site-packages\django\core\management\commands\syncdb.py", line 96, in handle_noargs
    sql, references = connection.creation.sql_create_model(model, self.style, seen_models)
  File "C:\Users\amira_000\virtualenv\vePy27\lib\site-packages\django\db\backends\creation.py", line 83, in sql_create_model
    model, f, known_models, style)
TypeError: sql_for_inline_foreign_key_references() takes exactly 4 arguments (5 given)

This is exactly the same as the following bug for Python's MySql connector.
http://bugs.mysql.com/bug.php?id=71229

Truth is, I don't know whether I'd rather fill this issue in FDB project.

Whe i follow the link Blog Posts in the admin area of Mezzanine 3.0.x and django 1.6.2

http://mariuz.android-dev.ro/admin/blog/blogpost/

I get this error
'module' object has no attribute 'SQLDateTimeCompiler'

https://gist.github.com/mariuz/a6b485a3b8f6de319e52

The test on BinaryField fails saving binary data.

Example:

class DataModel(models.Model):
    short_data = models.BinaryField(max_length=10, default=b'\x08')
    data = models.BinaryField()

from django.utils import six
from model_fields.models import *

binary_data = b'\x00\x46\xFE'

data_set = (binary_data, six.memoryview(binary_data))

for bdata in data_set:
... print bdata
... dm = DataModel(data=bdata)
... dm.save()

This generate

INSERT INTO "MODEL_FIELDS_DATAMODEL" ("SHORT_DATA", "DATA") VALUES (%s, %s) RETURNING "MODEL_FIELDS_DATAMODEL"."ID"
 ('\x08', <read-only buffer for 0x97293c8, size -1, offset 0 at 0x9730da0>)

Traceback (most recent call last): (splited)
File "/usr/local/lib/python2.7/dist-packages/fdb/fbcore.py", line 3574, in execute
self._ps._execute(parameters)
File "/usr/local/lib/python2.7/dist-packages/fdb/fbcore.py", line 3258, in _execute
self.__Tuple2XSQLDA(self._in_sqlda, parameters)
File "/usr/local/lib/python2.7/dist-packages/fdb/fbcore.py", line 3119, in __Tuple2XSQLDA
blob = ctypes.create_string_buffer(value)
File "/usr/lib/python2.7/ctypes/init.py", line 68, in create_string_buffer
raise TypeError(init)
TypeError: F�