On 17/01/2017 14:19, Dimitry Sibiryakov wrote: > 17.01.2017 17:07, Adriano dos Santos Fernandes wrote: >> Statement may already be prepared and allowed to be used not only in >> this dirty transaction, but in others one. > I would say that some kind "statement-level metadata consistency" should > be used for > such cases: statement to see metadata in state which they had at prepare time > (using its > own little metadata cache). It has a sense because IMessageMetadata for this > statement was > already returned to caller and must be obeyed. > Thus such statement could work in "dirty transaction" above even if the > function > already dropped. >
>From these two, I know the later is the worse thing can happen in a production environment: - A database with can't be updated due to locks - A updated database which code running various versions of changed logic depending on when statements was prepared and cached Adriano ------------------------------------------------------------------------------ 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
