O
Oleg Broytman
Hello!
I'm pleased to announce version 0.12.0, the first stable release of
branch 0.12 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/0.12.0
News and changes:
http://sqlobject.org/News.html
What's New
==========
Features & Interface
--------------------
* .selectBy(), .deleteBy() and .by*() methods pass all values through
.from_python(), not only unicode.
* The user can choose a DB API driver for SQLite by using a "backend"
parameter in DB URI or SQLiteConnection that can be a comma-separated
list of backend names. Possible backends are: "pysqlite2" (alias
"sqlite2"), "sqlite3", "sqlite" (alias "sqlite1"). Default is to test
pysqlite2, sqlite3 and sqlite in that order.
* The user can choose a DB API driver for PostgreSQL by using a "backend"
parameter in DB URI or PostgresConnection that can be a comma-separated
list of backend names. Possible backends are: "psycopg2", "psycopg1",
"psycopg" (tries psycopg2 and psycopg1), "pygresql". Default is
"psycopg".
WARNING: API change! PostgresConnection's parameter
"usePygresql" is now replaced with "backend=pygresql".
* The user can choose a DB API driver for MSSQL by using a "backend"
parameter in DB URI or MSSQLConnection that can be a comma-separated list
of backend names. Possible backends are: "adodb" (alias "adodbapi") and
"pymssql". Default is to test adodbapi and pymssql in that order.
* alternateMethodName is defined for all unique fields, not only alternateID;
this makes SQLObject create .by*() methods for all unique fields.
* SET client_encoding for PostgreSQL to the value of "charset" parameter
in DB URI or PostgresConnection.
* TimestampCol() can be instantiated without any defaults, in this case
default will be None (good default for TIMESTAMP columns in MySQL).
Small Features
--------------
* Imported DB API drivers are stored as connection instance variables, not
in global variables; this allows to use different DB API drivers at the
same time; for example, PySQLite2 and sqlite3.
* Removed all deprecated attribute and functions.
* Removed the last remained string exceptions.
For a more complete list, please see the http://sqlobject.org/News.html
Oleg.
I'm pleased to announce version 0.12.0, the first stable release of
branch 0.12 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/0.12.0
News and changes:
http://sqlobject.org/News.html
What's New
==========
Features & Interface
--------------------
* .selectBy(), .deleteBy() and .by*() methods pass all values through
.from_python(), not only unicode.
* The user can choose a DB API driver for SQLite by using a "backend"
parameter in DB URI or SQLiteConnection that can be a comma-separated
list of backend names. Possible backends are: "pysqlite2" (alias
"sqlite2"), "sqlite3", "sqlite" (alias "sqlite1"). Default is to test
pysqlite2, sqlite3 and sqlite in that order.
* The user can choose a DB API driver for PostgreSQL by using a "backend"
parameter in DB URI or PostgresConnection that can be a comma-separated
list of backend names. Possible backends are: "psycopg2", "psycopg1",
"psycopg" (tries psycopg2 and psycopg1), "pygresql". Default is
"psycopg".
WARNING: API change! PostgresConnection's parameter
"usePygresql" is now replaced with "backend=pygresql".
* The user can choose a DB API driver for MSSQL by using a "backend"
parameter in DB URI or MSSQLConnection that can be a comma-separated list
of backend names. Possible backends are: "adodb" (alias "adodbapi") and
"pymssql". Default is to test adodbapi and pymssql in that order.
* alternateMethodName is defined for all unique fields, not only alternateID;
this makes SQLObject create .by*() methods for all unique fields.
* SET client_encoding for PostgreSQL to the value of "charset" parameter
in DB URI or PostgresConnection.
* TimestampCol() can be instantiated without any defaults, in this case
default will be None (good default for TIMESTAMP columns in MySQL).
Small Features
--------------
* Imported DB API drivers are stored as connection instance variables, not
in global variables; this allows to use different DB API drivers at the
same time; for example, PySQLite2 and sqlite3.
* Removed all deprecated attribute and functions.
* Removed the last remained string exceptions.
For a more complete list, please see the http://sqlobject.org/News.html
Oleg.