Here is my story about migrating one app from django 1.1.x to 1.2.x using firebird-django 1.2 branch
Hello everyone, I want to make a summary of the changes implemented in
recent times about the project django-firebird:
* More complete exception error messeges (ported from pre-django 1.0
* Added a new attribute to obtain the version of Firebird. Useful to
ensure compatibility with firebird 1.5 and 2.x
* Implemented the proper support for data conversion. (Issue 8)
* Fixed bug on with_limits parameter on FirebirdQuery.as_sql. (Issue 9)
* Fixed bug on autoinc implementation (Issue 3)
* CHAR is mapped to CharField now (formerly TextField) – (Issue 6)
* NUMERIC/DECIMAL are mapped to DecimalField now (formerly Integer) –
* Correct interpretation of RDB$FIELD_SCALE for NUMERIC/DECIMAL fields –
* Correct consideration of is_null behaviour at field level – (Issue 6)
* Correct FOREIGN KEY evaluation in get_relations() – (Issue 6)
* Support for UNIQUE indices for UNIQUE – (Issue 6)
* Clean and better source code organization.
Remember, this software is still in alpha version, use it at your own risk.
Feel free to try and make any comments on this subject.
We need to add more experience with django and firebird to resolve some
issues. Any help will be apreciated.
Although not being a Python Geek, I gave Django a try, and I must admit, I’m impressed on how fast one can build a simple web-based master data management application with it. It’s pretty much defining an Django object model, which represents the tables, fields and relationships in your database. By enabling Django’s auto-generated admin site/area based on this model, this is all you need to access, delete, insert and update data in your database.