On Dec 17, 2005, at 5:25 PM, Phillip J. Eby wrote:
> Yeah, that was the thing, I don't think we wanted to guarantee
> thread affinity across yields, either in the sense of restricting a
> thread for one app *or* an app to one thread.
>
> This does mean that iterator-based apps can't rely on thr
James Y Knight wrote:
> I'm worried about database access. Most DBAPI adapters have
> threadsafety level 2: "Threads may share the module and
> connections.". So with those, at least, it should be fine to move a
> connection between threads, since "share OK" implies "move OK".
> However, no
On 12/18/05, Ian Bicking <[EMAIL PROTECTED]> wrote:
> James Y Knight wrote:
> > Does anybody have practical experience with the safety of moving a
> > DBAPI cursor between threads?
>
> I haven't done that, but SQLite (2?) notably doesn't allow you to move a
> connection between threads. I'm not ac
Ian Bicking wrote:
> James Y Knight wrote:
>> I'm worried about database access. Most DBAPI adapters have
>> threadsafety level 2: "Threads may share the module and
>> connections.". So with those, at least, it should be fine to move a
>> connection between threads, since "share OK" implies "
On Dec 18, 2005, at 6:57 PM, M.-A. Lemburg wrote:
> Ian Bicking wrote:
>
>> James Y Knight wrote:
>>
>>> I'm worried about database access. Most DBAPI adapters have
>>> threadsafety level 2: "Threads may share the module and
>>> connections.". So with those, at least, it should be fine to move a
>
