[DB-SIG] SQLObject 2.0
phd at phdru.name
Sat Dec 20 19:20:19 CET 2014
I'm pleased to announce version 2.0.0, the first stable release of branch
2.0 of SQLObject.
What's new in SQLObject
Features & Interface
* DateTimeCol and TimeCol can read and write values with microseconds.
WARNING: microseconds are supported by MariaDB since version 5.3.0 and
by MySQL since version 5.6.4, and even these versions require special
handling: columns to store microseconds have to be declared with
precision 6: TIME(6), DATETIME(6), TIMESTAMP(6). SQLObject does the
right thing when creating a new database but existing databases have
to be changed: run something like
``ALTER TABLE name MODIFY COLUMN col TIME(6)`` for every column that
you want to store microseconds.
WARNING: backward compatibility problem! Date/Time columns created
with microseconds cannot be read back from SQLite databases (and
perhaps other backends) with versions of SQLObject older than 1.7.
* PostgresConnection, when used with fromDatabase=True, sets alternateID
for unique columns.
* Extend sdist: include everything (even generated html)
into source distribution.
* Extend setup.py: include docs and tests into the egg.
* Development was switched from Subversion to git.
* Old news were restored back to version 0.2.1.
* News.txt was split into 5 small files.
Contributors for this release are Andrew Trusty and Jared Jennings.
For a more complete list, please see the news:
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).
Python 2.6 or 2.7 is required.
Where is SQLObject
News and changes:
Oleg Broytman http://phdru.name/ phd at phdru.name
Programmers don't die, they just GOSUB without RETURN.
More information about the DB-SIG