On 27.08.2018 20:10, Adriano dos Santos Fernandes wrote:
All,
Please. If nobody else sees the magnitude of this problem, I'll shut up.
What we talk here is something that is being said to fix read committed,
but completely destroys it.
Adriano, I agree that calling function multiple times when it appears at
the first glance to be called only once is not good. But in this thread
were provided a lot of examples of that behavior that do not depend upon
read consistency and were in effect since interbase times. And nobody,
never (at least I do not remember it) used to cry in
devel/support/tracker/etc that it's awful. May be problem is not as
tragic as you see it?
On the other hand - yes, sometimes performing some actions once and only
once is necessary. Internally that are DDL-related changes and post
messages. May be we should think about providing an ability to access
DFW stage of transaction from UDR? In your example with file creation in
many (certainly not all, but many and sooner of all typical cases) file
should be written only in a case when transaction is commited
successfully. Same applies to sending eMail and a lot of other cases
when SQL needs to interact with outer world.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
