> It is good to know you solved your task. The only thing I do not
> understand is why do you create tables using SQL commands. Thanks to
> the great work of the people around SQLobjects it just a piece of
> cake to create your any table using SQLobject:

I can't speak for him, but I can speak for myself.   ORMs only get you
so far when it comes to maintaining databases schemas in production

A production database often has to be up 100% of the time.

During an upgrade there is almost always a period where two versions
of the application are using the same database.  In these cases the new
schema has to support both versions application versions.
There are often schema entities outside of SQLobject's purview that have
to be maintained.   Among these are grants, users, triggers, and stored

All of this has to be done while the database is live.  The simplest
way of doing this is a series of SQL patches which are applied to the
Thanks for your posting.

Yep. You are right and I do understand above mentioned. In our company we are doing (mainly because of historical reasons) backup/update maintenance (including SQL meta data ) every night - Firebird SQL engine.

But my feeling was it is out of the scope of discussed topic. We were discussed one table with two columns :-). So I had a feeling for such a simple example and for the "educational purposes" it is not necessary to be bothered with SQL.

Anyway IMHO this why the SQLobject is here. To hide "pure SQL" as fare as possible and to give an "object" approach to the Python users.

Petr Jakes