Opened 19 years ago

Last modified 6 years ago

#301 enhancement closed fixed (fixed)

enterprise connectionpool - documentate run* - Methods

Reported by: malamute Owned by:
Priority: normal Milestone:
Component: Keywords:
Cc: Dave Peticolas, itamarst, malamute Branch:


Attachments (1) (1.8 KB) - added by malamute 19 years ago.

Download all attachments as: .zip

Change History (11)

Changed 19 years ago by malamute

comment:1 Changed 19 years ago by malamute

I only copied the normal execute - part and changed it to 
executemany (also the doc-strings). I tested it on MySQLdb 
0.9.2 and it seems to work fine.

comment:2 Changed 19 years ago by itamarst

runInteraction should cover this use case adequately, I

If this is the case, please close the bug, or change the
title to "runInteraction needs better documentation" ;)

comment:3 Changed 19 years ago by malamute

Ok. runInteraction solves that problem quiet good. So this should really be
better documentaded. I will see if i can write a little documentation in the
next week about the run* - statments in ConnectionPool, because if i knew that
before i would have done many things diffrent. I think other people will go in
the same trap.

Thank you

comment:4 Changed 19 years ago by Dave Peticolas

Thank you, better documentation would be nice since
you're definitely not the first person to miss runInteraction
on the first pass.

comment:5 Changed 19 years ago by itamarst

I added example of runInteraction.

comment:6 Changed 19 years ago by itamarst

And the API docs are now generated correctly so you can see docs for run* methods.

comment:7 Changed 19 years ago by radix

shouldn't this issue be resolved?

comment:8 Changed 19 years ago by Dave Peticolas

Yes, I think the new docs should cover this issue.

comment:9 Changed 11 years ago by <automation>

Owner: Dave Peticolas deleted

comment:10 Changed 6 years ago by GitHub <noreply@…>

In ebcabbb:

Error: Processor CommitTicketReference failed
 does not appear to be a Git repository. See the log for more information.
Note: See TracTickets for help on using tickets.