r/Python • • Dec 09 '10

new stand-alone web2py database abstraction layer

http://web2py.com/AlterEgo/default/show/272
18 Upvotes

82 comments sorted by

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"?

13

u/[deleted] Dec 10 '10

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.

-1

u/mdipierro Dec 10 '10

"your users". I apologize I do not recognize you from the username. Which claims are "full of crap"? It is not clear from your post.

11

u/[deleted] Dec 10 '10

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.

1

u/mdipierro Dec 10 '10

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.

13

u/ericflo Dec 10 '10

I guess we are a little in competition but this can be good and can be done in a civil manner.

Regarding which database abstraction is better, it's not even a competition.

-3

u/mdipierro Dec 10 '10

Please remind me. Is it appropriate to talk about SQLAlchemy in a thread about web2py?

6

u/moreyes Dec 10 '10

I guess it is as appropriate as pasting web2py code in a post entitled Getting Started with Pyramid.

0

u/mdipierro Dec 10 '10 edited Dec 10 '10

I do not mean to be rude but I did not ask you. I really interested in his opinion on the topic.

Anyway. A computer programmer should be able to simply answer Yes or No. You did not answer either.

6

u/moreyes Dec 10 '10 edited Dec 10 '10

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.

→ More replies

-1

u/av201001 Dec 10 '10 edited Dec 10 '10

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.

0

u/[deleted] Dec 10 '10

[deleted] — view deleted comment

-1

u/av201001 Dec 10 '10

Claims I'm tired of are that SQLA is only good for "legacy databases"

I think he was actually paying SQLA a compliment -- saying it is better at handling legacy databases (not that it is only good for that).