Thread: [SQLObject] SQLObject 0.13.0b1
SQLObject is a Python ORM.
Brought to you by:
ianbicking,
phd
From: Oleg B. <ph...@ph...> - 2010-07-15 15:58:24
|
Hello! I'm pleased to announce version 0.13.0b1, the first beta version of a new upcoming release of branch 0.13 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.13.0b1dev-r4218 News and changes: http://sqlobject.org/News.html What's New ========== News since 0.12 --------------- Features & Interface ~~~~~~~~~~~~~~~~~~~~ * SQLObject instances that don't have a per-instance connection can be pickled and unpickled. * Validators became stricter: StringCol and UnicodeCol now accept only str, unicode or an instance of a class that implements __unicode__ (but not __str__ because every object has a __str__ method); BoolCol accepts only bool or int or an instance of a class that implements __nonzero__; IntCol accepts int, long or an instance of a class that implements __int__ or __long__; FloatCol accepts float, int, long or an instance of a class that implements __float__, __int__ or __long__. * Added a connection class for rdbhost.com (commercial Postgres-over-Web service). Small Features ~~~~~~~~~~~~~~ * Added TimedeltaCol; currently it's only implemented on PostgreSQL as an INTERVAL type. * Do not pollute the base sqlmeta class to allow Style to set idName. In the case of inherited idName inherited value takes precedence; to allow Style to set idName reset inherited idName to None. * Better handling of circular dependencies in sqlobject-admin - do not include the class in the list of other classes. * Renamed db_encoding to dbEncoding in UnicodeStringValidator. * A new parameter 'sslmode' was added to PostgresConnection. For a more complete list, please see the news: http://sqlobject.org/News.html Oleg. -- Oleg Broytman http://phd.pp.ru/ ph...@ph... Programmers don't die, they just GOSUB without RETURN. |
From: Oleg B. <ph...@ph...> - 2010-07-15 16:05:28
|
On Thu, Jul 15, 2010 at 07:58:08PM +0400, Oleg Broytman wrote: > I'm pleased to announce version 0.13.0b1, the first beta version of a new > upcoming release of branch 0.13 of SQLObject. There a few major changes in the branch so it needs to have a longer beta period. > * Validators became stricter: StringCol and UnicodeCol now accept only str, > unicode or an instance of a class that implements __unicode__ (but not > __str__ because every object has a __str__ method); BoolCol accepts only > bool or int or an instance of a class that implements __nonzero__; IntCol > accepts int, long or an instance of a class that implements __int__ or > __long__; FloatCol accepts float, int, long or an instance of a class > that implements __float__, __int__ or __long__. I want to explain: with this I want to prevent things like class MyTable(SQLObject): name = StringCol() age = IntCol() flag = BoolCol() row = MyTable(name=10, age='42', flag={}) I understand this is a controversial change. I can put arguments on both sides, pro et contra. If there will be complaints I will reverse the decision. Oleg. -- Oleg Broytman http://phd.pp.ru/ ph...@ph... Programmers don't die, they just GOSUB without RETURN. |
From: Daniel F. <fet...@go...> - 2010-07-16 07:53:20
|
>> I'm pleased to announce version 0.13.0b1, the first beta version of a new >> upcoming release of branch 0.13 of SQLObject. > > There a few major changes in the branch so it needs to have a longer > beta period. > >> * Validators became stricter: StringCol and UnicodeCol now accept only >> str, >> unicode or an instance of a class that implements __unicode__ (but not >> __str__ because every object has a __str__ method); BoolCol accepts only >> bool or int or an instance of a class that implements __nonzero__; >> IntCol >> accepts int, long or an instance of a class that implements __int__ or >> __long__; FloatCol accepts float, int, long or an instance of a class >> that implements __float__, __int__ or __long__. > > I want to explain: with this I want to prevent things like > > class MyTable(SQLObject): > name = StringCol() > age = IntCol() > flag = BoolCol() > > row = MyTable(name=10, age='42', flag={}) > > I understand this is a controversial change. I can put arguments on both > sides, pro et contra. If there will be complaints I will reverse the > decision. I think this is a reasonable change. Cheers, Daniel -- Psss, psss, put it down! - http://www.cafepress.com/putitdown |