O
Oleg Broytman
Hello!
I'm pleased to announce version 1.1.0, the first stable release of branch
1.1 of SQLObject.
What is SQLObject
=================
SQLObject is an object-relational mapper. Your database tables are described
as classes, and rows are instances of those classes. SQLObject is meant to be
easy to use and quick to get started with.
SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite,
Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB).
Where is SQLObject
==================
Site:
http://sqlobject.org
Development:
http://sqlobject.org/devel/
Mailing list:
https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss
Archives:
http://news.gmane.org/gmane.comp.python.sqlobject
Download:
http://cheeseshop.python.org/pypi/SQLObject/1.1.0
News and changes:
http://sqlobject.org/News.html
What's New
==========
Features & Interface
--------------------
* SelectResults (returned from .select()) is allowed in IN(column, list).
* A different workaround is used in SQLiteConnection to prevent PySQLite
from converting strings to unicode - in the case of a registered text
conversion function PySQLite silently converts empty strings to Nones;
now SQLObject uses text_factory instead and properly returns empty
strings.
* It is now possible to declare one encoding for all UnicodeCol's per
table (as sqlmeta.dbEncoding) or per connection (as connection.dbEncoding).
Default (if dbEncoding is found neither in column nor in table nor in
connection) is 'utf-8'.
Source code and internals
-------------------------
* Decorators @classmethod and @staticmethod are used everywhere.
* All 'mydict.has_key(name)' checks were replaced with 'name in mydict'.
For a more complete list, please see the http://sqlobject.org/News.html
Oleg.
I'm pleased to announce version 1.1.0, the first stable release of branch
1.1 of SQLObject.
What is SQLObject
=================
SQLObject is an object-relational mapper. Your database tables are described
as classes, and rows are instances of those classes. SQLObject is meant to be
easy to use and quick to get started with.
SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite,
Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB).
Where is SQLObject
==================
Site:
http://sqlobject.org
Development:
http://sqlobject.org/devel/
Mailing list:
https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss
Archives:
http://news.gmane.org/gmane.comp.python.sqlobject
Download:
http://cheeseshop.python.org/pypi/SQLObject/1.1.0
News and changes:
http://sqlobject.org/News.html
What's New
==========
Features & Interface
--------------------
* SelectResults (returned from .select()) is allowed in IN(column, list).
* A different workaround is used in SQLiteConnection to prevent PySQLite
from converting strings to unicode - in the case of a registered text
conversion function PySQLite silently converts empty strings to Nones;
now SQLObject uses text_factory instead and properly returns empty
strings.
* It is now possible to declare one encoding for all UnicodeCol's per
table (as sqlmeta.dbEncoding) or per connection (as connection.dbEncoding).
Default (if dbEncoding is found neither in column nor in table nor in
connection) is 'utf-8'.
Source code and internals
-------------------------
* Decorators @classmethod and @staticmethod are used everywhere.
* All 'mydict.has_key(name)' checks were replaced with 'name in mydict'.
For a more complete list, please see the http://sqlobject.org/News.html
Oleg.