On Dec 25, 2007 5:31 PM, Tom Berger <[EMAIL PROTECTED]> wrote:
> On 25/12/2007, Anand Chitipothu <[EMAIL PROTECTED]> wrote:
>
> >
> > Many times I felt the need to specify database schema in a DB neutral
> > way, so that the application I am building can be used with any
> > database.
> > I think web.py should have some way to do this.
>
> http://www.sqlalchemy.org/ does stuff like that.

It does, but it is too heavy to include in web.py. There are
somethings that I personally don't like about SQLAlchemy.
In SQLAlchemy, a table has to be associated with a metadata when it is
created, which makes it difficult to take tables from different places
and assemble a schema. For example, you may want to create you blog
application by taking session table from web.py, user tables from some
auth module and define blog and post tables your self. Which I find
not very easy to do with SQLAlchemy.

Also, I didn't find an easy way to extend it. I even tried to look at
the source code and felt that it is not very easy.

> There's something slightly nasty about specifying the schema like that,
> because when you read it you have to 'translate' the declarative Python code
> to SQL in your head in order to understand it.

I am trying to make that smooth by being close to one db engine.

> It should be possible to
> write schemas using a safe, vendor neutral subset of SQL, and if there are
> many features you can't get that way, maybe a translator from some kind of
> neutral SQL to the variants supported by all the different vendors would be
> a nice thing to have (and useful beyond just web.py and even Python).

I think, thats what I am trying to do.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"web.py" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/webpy?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to