i chose a simple example, rather than get into the overall complexities =
of my entire situation.. no need to get into the guts, when a simple =
test will suffice...
you kept wanting to assume that i should simply create the tbl in =
sqlobject, when my situation already has a pretty extensive db schema...
in my experience... wrappers, and apps that sit on top of the db are =
useful, but have their place.. and at times, they're implemented by =
people who really don't want to get their hands 'dirty' with the =
underlying stuff (db cmds...). in some cases, the use of the wrapper may =
even lead to an imposition on the overall app, because you're more or =
less forced to follow the wrapper's developer's mentality/approach...
but anyway.. .thanks!!
From: sqlobject-discuss-bounces@... =
[mailto:sqlobject-discuss-bounces@... Behalf Of =
Sent: Thursday, January 03, 2008 12:57 AM
To: Jeff Younker
Subject: Re: [SQLObject] sqlobject - python question/issue
> It is good to know you solved your task. The only thing I do not=20
> 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=20
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=20
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=20
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 =
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.=20
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.