a really solid, perhaps unique, library that, as far as i can tell, completely addresses the "impedence mismatch" argument. if you're directly using a database api in a structured way, you've probably already reimplemented the sqlalchemy core, and refactoring your program to use sqlalchemy will give you an orm, should you want one, and make your code portable across database implementations even if you don't. if you're already using an orm, refactoring to use sqlalchemy will allow you to to start optimizing the low-level database operations in a coherent way (i.e. not just sprinkling SQL throughout the models). there's a nice writeup in the architecture of open source applications ( <a href="http://www.aosabook.org/en/sqlalchemy.html" rel="nofollow">http://www.aosabook.org/en/sqlalchemy.html</a> )<p>now, fantods aside, is there anything like this for java? according to the aosa writeup, sqlalchemy's author found python's multiple inheritance useful for implementing certain ideas, so porting probably isn't straightforward. also, the relevant stackoverflow question ( <a href="http://stackoverflow.com/questions/10537766/closest-equivalent-to-sqlalchemy-for-java-scala" rel="nofollow">http://stackoverflow.com/questions/10537766/closest-equivale...</a> ) seems inconclusive.<p>this is not to criticize java as a language, but rather because <i>i really wish there was something like sqlalchemy for java</i>.
> support for Postgresql JSON types,<p>This. Finally :) I know I was searching this a few months ago and there was a long due ticket for this to be added. Thank you whoever did this patch.<p>A side note. I personally use Pyramid (I use Pyramid more, however) and Flask. For Flask project I never use flask-sqlalchemy because mitsuhiko doesn't seem to update the repository as often as he should. A lot of outstanding tickets and pull requests. Some are merged but they are never closed. So I always end up bringing up SQLAlchemy myself into Flask because I just don't trust the library. Is that how people feel too? For Pyramid, SQLAclemy is the "standard" ORM to use and with ini file it is supposed easy to integrate SA into Pyramid app.
sqlalchemy is the best database toolkit for python developers. you can use it as an orm or you can just use its core functionality; write sql expressions in python, define your tables, columns and types. anything you can think of, in terms of dbs, you can do with sqlalchemy.<p>i'd like to take a moment and thank to @zzeeek [1][2] and all of the contributors.<p>[1] <a href="https://news.ycombinator.com/user?id=zzzeek" rel="nofollow">https://news.ycombinator.com/user?id=zzzeek</a><p>[2] <a href="https://twitter.com/zzzeek" rel="nofollow">https://twitter.com/zzzeek</a>
Thanks for this release. Learning SQL before ever touching an ORM, SQLAlchemy's approach makes a lot more sense to me than something "simplier" like Django's ORM.<p>Anyone know, is there any chance Django would pull in SQLAlchemy core as a dependency and implement their ORM on top of it?
I dunno. I just don't get ORMs. I certainly see their use case in easy prototyping, but with the advent of NoSQL, why not just prototype with MongoDB, or similar, and if it turns out your data is close to uniform in structure, just switch over to MySQL, or similar.<p>To keep my code portable, I stick to standard SQL and don't use any stored procedures. I'm sure this is probably not a tenable strategy for web-scale apps, but with 100s/1000s of users and only millions of records, it seems to work just fine.<p>This comment is no way meant to disparage SQLAlchemy which by all accounts seems to be a first rate work of engineering. I am speaking of ORMs in general, and why should we use them.
Why is SQLAlchemy still under 1.0? Are there good reasons, or is it just the apparently typical (and typically irrational) fear of the version number "1.0"?