Django 1.1 beta released

http://www.djangoproject.com/weblog/2009/mar/23/11-beta-1/

by zain • 17 years ago

95 12 17 years ago

jacobian3• 17 years ago

The interesting details are in the release notes: http://docs.djangoproject.com/en/dev/releases/1.1-beta-1/

bmelton• 17 years ago

I'll say. I haven't been keeping up with the development, but the improvements to the model layer alone are worth the price of admission.

The conditional view processing is another gem, though I'm not sure it'll supplant a real caching engine -- it should at least get wins for those who either opt out of something like memcache, or perhaps haven't gotten around to it yet. Of course, adding it as a supported backend, I can't imagine that happening very often.

jacobian3• 17 years ago

I'd view the conditional view processing as complimentary to the cache engine; you can't have too many layers of caching really. Also, conditional view processing can save bandwidth since unmodified responses don't need a body. Bandwidth is a lot cheaper now than just a few years ago, but for some folks this is still a bug deal.

Also, one important "feature" you get for free when using conditional view rendering is that upstream caches -- Varnish, Squid, etc. -- will perform better as well.

So really this new feature is about improving how well Django speaks HTTP, not caching per-se.

snprbob86• 17 years ago

I'm still not entirely clear on what the benefits of Django's ORM are. isn't SqlAlchemy far more mature and feature rich? Why aren't they moving closer to that?

pistoriusp• 17 years ago

I'm also very happy about with the editable fields on the change list.

hajrice• 17 years ago

WOW! This is awesome!

elv• 17 years ago

I hope they keep focus on simplicity and usability that proxy model thing seems complex and bugmaker to me

jacobian3• 17 years ago

It's a pretty esoteric feature, I'll grant you, but it's needed to implement several useful, more user-oriented features. The big one is deferred fields, which in certain situations can give apps enormous performance gains. If you're interested in how these features are related, Malcolm lays it all out here: http://www.pointy-stick.com/blog/2009/03/23/yak-shaving-adva...

It's important to understand that often the simplest features have the most complex underpinnings. In other words, simple APIs often require complicated internals.

gregparadee• 17 years ago

Aggregation support alone is worth the upgrade.

woadwarrior01• 17 years ago

One thing I'd noticed a while back was that it tends to generate LEFT OUTER JOINS instead of plain old LEFT JOINS, which isn't really bad, But thats one of the reasons (besides just being plain lazy) that I'm still sticking with pl/pgsql functions for most of my aggregation needs.

Django 1.1 beta released

Related Stories