Re: [Firebird-devel] Providers, yvalve, external engines and object lifecycle

[Adriano d. S. F. <adr...@gm...>]

On 28-03-2011 15:28, Vlad Khorsun wrote:
>>>> The user should not call detach and another methods simultaneously,
>>>> never. Why the heck they would do it? This is user application problem.
> 
>     Do you offer us to undo thread-safety changes made in v2.5 client library ? :)
> 
I believe you're too optimistic about thread-safety. No bug reports may
not means no problem, it may be because nobody tries to crash "inside
our code".

Do you really think that isc_dsql_prepare and isc_dsql_free_statement
are thread safe when both used concurrent in a same statement handle?

This is a question open to finalize my changes.

Do we really need to allow simultaneous calls on the same attachment in
yvalve, since they're going to be blocked (serialized) in another
(remote - not sure, engine - sure) providers?

If we say yes, we must do it correct, but current and 2.5 code doesn't
look like to be.


Adriano