Thread: [SQLObject] SQLObject 1.0.0b1

Hello!

I'm pleased to announce version 1.0.0b1, the first beta of the upcoming
release of branch 1.0 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.0.0b1dev-r4354

News and changes:
http://sqlobject.org/News.html


What's New
==========

Features & Interface
--------------------

* Major API change: DB URI parser was changed to use urllib.split*() and
  unquote(). This means any username/password/path are allowed in DB
  URIs if they are properly %-encoded, and DB URIs are automatically
  unquoted.

* In SQLite, id columns are made AUTOINCREMENT.

* Parameter ``backend`` in DB URI is no longer supported, use parameter
  ``driver``.

For a more complete list, please see the news:
http://sqlobject.org/News.html

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

On Wed, Mar 09, 2011 at 05:47:26PM +0300, Oleg Broytman wrote:
> * Major API change: DB URI parser was changed to use urllib.split*() and
>   unquote(). This means any username/password/path are allowed in DB
>   URIs if they are properly %-encoded, and DB URIs are automatically
>   unquoted.

   I have been trying to preserve backward compatibility as much as
possible. Most URIs are not affected at all. Dirty trick with w32 paths
(C|/path instead of C:/path) is still supported, though C:/path is now
the recommended syntax. Old API is preserved:
connectionForURI(uri, oldUri=True), DBConnection.connectionFromOldURI(),
DBConnection.oldURI(). There is a script sqlobject-convertOldURI that
accepts old-style URI at the command line and prints to stdout the URI
in the new format.
   Anyway - a prolonged beta period.

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

>> * Major API change: DB URI parser was changed to use urllib.split*() and
>>   unquote(). This means any username/password/path are allowed in DB
>>   URIs if they are properly %-encoded, and DB URIs are automatically
>>   unquoted.
>
>    I have been trying to preserve backward compatibility as much as
> possible. Most URIs are not affected at all. Dirty trick with w32 paths
> (C|/path instead of C:/path) is still supported, though C:/path is now
> the recommended syntax. Old API is preserved:
> connectionForURI(uri, oldUri=True), DBConnection.connectionFromOldURI(),
> DBConnection.oldURI(). There is a script sqlobject-convertOldURI that
> accepts old-style URI at the command line and prints to stdout the URI
> in the new format.
>    Anyway - a prolonged beta period.

Wooohoooo! Version 1.0 beta! :)

My app works perfectly with the new version!

Thanks a million,
Daniel

-- 
Psss, psss, put it down! - http://www.cafepress.com/putitdown

On Wed, Mar 09, 2011 at 07:40:27PM +0100, Daniel Fetchinson wrote:
> Wooohoooo! Version 1.0 beta! :)
> 
> My app works perfectly with the new version!

   Thank you for the report!

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.