Django 1.6 alpha 1 released
djangoproject.com
Django 1.6 alpha 1 released
1–10 of 36 posts
Re: Django 1.6 alpha 1 released
#2Good. Keep it coming. For those who are interested further, here are the release notes to see "What’s new in Django 1.6" http://j.mp/13XRnoD
Re: Django 1.6 alpha 1 released
#3This is the most exciting and interesting thing in the release:
Persistent database connections
Django now supports reusing the same database connection for several requests. This avoids the overhead of re-establishing a connection at the beginning of each request. For backwards compatibility, this feature is disabled by default. See Persistent connections for details.
Re: Django 1.6 alpha 1 released
#4This is the most exciting and interesting thing in the release: Persistent database connections Django now supports reusing the same database connection for several requests. This avoids the overhead of re-establishing a connection at the beginning of each request. For backwards compatibility, this feature is disabled by default. See Persistent connections for details.
> This is the most exciting and interesting thing in the release:
Absolutely. My expectation is that this alone should dramatically increase app response times for any reasonably DB-dependant application.
Re: Django 1.6 alpha 1 released
#5Good. Keep it coming. For those who are interested further, here are the release notes to see "What’s new in Django 1.6" http://j.mp/13XRnoD
Unshortened URL for the release notes: https://docs.djangoproject.com/en/dev/releases/1.6/
Re: Django 1.6 alpha 1 released
#6This is the most exciting and interesting thing in the release: Persistent database connections Django now supports reusing the same database connection for several requests. This avoids the overhead of re-establishing a connection at the beginning of each request. For backwards compatibility, this feature is disabled by default. See Persistent connections for details.
Connection pooling? I am surprised to find out that Django doesn't have this feature until now. Is there any specific reason why this wasn't implemented much earlier? Old tech like plain asp had this more than a decade ago.
Re: Django 1.6 alpha 1 released
#7This is the most exciting and interesting thing in the release: Persistent database connections Django now supports reusing the same database connection for several requests. This avoids the overhead of re-establishing a connection at the beginning of each request. For backwards compatibility, this feature is disabled by default. See Persistent connections for details.
So, when will we have prepared statements upon persistent connections? This would be the biggest speed up of all factors.
Re: Django 1.6 alpha 1 released
#8This is the most exciting and interesting thing in the release: Persistent database connections Django now supports reusing the same database connection for several requests. This avoids the overhead of re-establishing a connection at the beginning of each request. For backwards compatibility, this feature is disabled by default. See Persistent connections for details.
> This is the most exciting and interesting thing in the release: Absolutely. My expectation is that this alone should dramatically increase app response times for any reasonably DB-dependant application.
It does. You can currently do this with an external Django DB Pool module, for some numbers see: http://mixedbit.org/blog/2013/02/06/django_db_pool_on_heroku...
I also can't wait to have such mode fully supported by the core product.
Re: Django 1.6 alpha 1 released
#9This is the most exciting and interesting thing in the release: Persistent database connections Django now supports reusing the same database connection for several requests. This avoids the overhead of re-establishing a connection at the beginning of each request. For backwards compatibility, this feature is disabled by default. See Persistent connections for details.
Connection pooling? I am surprised to find out that Django doesn't have this feature until now. Is there any specific reason why this wasn't implemented much earlier? Old tech like plain asp had this more than a decade ago.
There are external apps that provide this.
https://github.com/gmcguire/django-db-pool https://github.com/kennethreitz/django-postgrespool
https://github.com/niwibe/djorm-ext-pool
Re: Django 1.6 alpha 1 released
#10Are there usually this many backwards-incompatible changes? In the past I've usually been able to upgrade Django without having to do any significant changes in the code.