Hi Emil,
On May 16, 2013, at 5:21 PM, Emil Stenström wrote:
> Any feedback on how I was thinking? Does it make sense?
>
> Based on the feedback so far I gather that changing the block tag is a bad
> idea. I'd love to continue working on this, because I've felt this need in
> lots of different
On 17 touko, 16:47, Alex Gaynor wrote:
> Right now Django absolutely does not close all cursors, if you look at
> django/db/models/sql/compiler.py def execute_sql (sorry, going from memory
> here) you'll see this. It'd be good if it did. There used to be some crazy
> stuff around reading chunks an
Right now Django absolutely does not close all cursors, if you look at
django/db/models/sql/compiler.py def execute_sql (sorry, going from memory
here) you'll see this. It'd be good if it did. There used to be some crazy
stuff around reading chunks and emitting those, now that I believe Anssi
has r
django-developers has over 7500 subscribers. Your message is relevant to at
most 4 of them. Unless it was plain spam. In either case, that's not cool,
avoid that in the future.
--
Aymeric.
On 16 mai 2013, at 11:51, Flower Platform Team
wrote:
> Hello GSoC Mentors,
>
> As you are particip
Hello GSoC Mentors,
As you are participating to Google Summer of Code, I'm wondering if you
could consider using Flower Dev Center [1] while working with students.
Flower Dev Center is an online platform for UML modeling diagramming,
with a strong focus on code synchronization, integration wi
Hi Vernon,
On 17 mai 2013, at 13:26, VernonCole wrote:
> After much debugging it looks like my database proxy server may be running
> out of worker threads: it uses one for each cursor.
With DB-API adapters, the connections are expected to be expensive and cursors
cheap. (If this sounds obs
Shai:
I think that you are showing how rotten this whole "paramstyle" mess is:
the thing you are describing is, IIUC, "pyformat" paramstyle. "named" uses
a ":name" SQL statement syntax, and expects a mapping of parameters. My
understanding was that Oracle expected that one. I am only an eg
My testing of remote mssql is proceeding nicely, or was until a few days
ago. After much debugging it looks like my database proxy server may be
running out of worker threads: it uses one for each cursor. My traces show
that, when running the test suite in django-mssql (using ./manage.py test)
