That's pretty cool!  I've attempted this in the past, but always ended
up with test case failures, and didn't see any speedups, so I
abandoned it.  I'll try this out when I have time.

Could someone repackage it as a proper patch attached to ticket #7732?

I think I'd rather see it folded into the trunk for the Oracle
backend, rather than as a separate backend.  We require cx_Oracle
4.3.1 or later, so there shouldn't be any issues with pooling support.
 But I suppose that relegates this to post-1.0.

Matt

On Jul 15, 2:38 pm, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:
> Hello!
>
> Last Saturday we've gathered in Moscow at Yandex and had a sprint aimed
> at newforms-admin bugs.
>
> It didn't work as smooth and effective that we hoped but all the
> problems are more or less explained by the lack of my experience as a
> sprint organizer. We'll try harder next time!
>
> Nonetheless... We worked on a few bugs which all tagged with the keyword
> "yandex-sprint"[1]. Many thanks to Honza Král who was on #django-sprint
> that day and promptly triaged our tickets. Now I'd like to ask someone
> of committers to take a look at them.
>
> One ticket deserves a special note. There were 3 guys who were working
> not on newforms-admin bugs but on a new Oracle backend with support for
> pooling connections. They did finish it and submitted it in Trac[2]. The
> ticket already has a note about repackaging the backend as a patch.
> However I think it worse to ask opinion of guys that support the
> official Oracle backend on what's better to do with this code: make it
> another backend, make it an external backend, replace current backend?
>
> Thanks!
>
> [1]:http://code.djangoproject.com/query?keywords=~yandex-sprint&order=pri...
> [2]:http://code.djangoproject.com/ticket/7732
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to