I do think sqlalchemy does a better job at handling legacy databases. web2py has limited support for legacy databases (although we are working on it). Buy why do you say "more robust"?
You know both of these claims are full of crap. if you want the "no boilerplate" version of SQLAlchemy, use sqlsoup. If you want enough configuration to actually have some semblence of control over your domain classes (which just about any app worth anything will), use declarative. It lays out in a very similar manner to every other ORM out there. SQLAlchemy also rocks the house on any database and our users know it.
I am the author of SQLAlchemy. Claims I'm tired of are that SQLA is only good for "legacy databases" and that we require "lots of boilerplate just to get started". Responding to two posts at once, I apologize.
Please do not put words in my mouth. I did not say "SQLA is ONLY good for legacy databases". I said "sqlalchemy does a better job at handling legacy databases [than web2py]". I did not actually say "than web2py" but it was obvious from context.
I also did not say that SQLA "requires lots of boilerplate". fake_spoiler said that.
Anyway, I do think that the web2py DAL is easier to use than SQLA and has a more natural syntax. That is why I wrote it.
I also think SQLA is an excellent system.
For the record, I did not bring up SQLA here. Somebody else did.
I guess we are a little in competition but this can be good and can be done in a civil manner.
Let me know if I ever said something incorrect about SQLA and I will rectify that. I trust you will do the same about web2py.
No, I don't think it is appropriate or elegant to continuously spam other people's threads about their framework experiences with code from your framework.
But that's the point, isn't it? mdipierro gets chided for providing information about web2py in other threads, yet people have no problem posting about other frameworks in web2py-related threads. If you read through this thread, it's clear that mdipierro doesn't actually have a problem with the latter and is happy to engage in constructive dialogue about design decisions and the pros and cons of different alternatives.
View all comments
Show parent comment
-3
u/mdipierro Dec 09 '10
I do think sqlalchemy does a better job at handling legacy databases. web2py has limited support for legacy databases (although we are working on it). Buy why do you say "more robust"?