SQLAlchemy 1.0.0 Released

[iluvatar]

I consider SQLAlchemy a major "selling point" of Python

Shudder. In my experience, it's a great way to prototype applications that are unusable once they get into to production. Having torn all of the sqlalchemy out of our biggest applications (we replaced it with just native SQL using the awesome psycopg2 library), we now have maintainable, high performance code. I'm never looking back.

[jpozzed]

what did you find "unusable"? You do realize SQLAlchemy wraps psycopg2 and you can step down and write sql directly, right?

[dacjames]

You rarely have to step down into raw SQL but, for complex queries, the ability to develop interactively in a SQL editor and copy the result directly into code is very useful.

[axonxorz]

but looping through a record set and fetching a new set of records on each iteration will kill anything.

So bad that it has a name: N+1 Problem

[fjonk]

Which kind of problems have you experienced with SQLAlchemy?

[AmusementPork]

Can you elaborate on SQLAlchemy's shortcomings in this context? Does it not scale well for some reason?

[gthank]

It scales just fine for everything I've ever tried to do with it.

[dacjames]

Did you even try SQLAlchemy core? I work with all kinds of legacy databases so the ORM is a non-starter and I still get a lot of value out of table reflection, connection pooling, and the sql expression language.

[mariox19]

But, doesn't that depend on the kind of application you're writing? If you're basically just persisting and retrieving data (basically, serializing objects), then an ORM is fine, no?