Hello Kjell, > I see noone replied. OK. > > > > 1. Alexey Kovyazin at IBSurgeon confirms that the problem still exists. > > He's the one who fixed my corruption before. He should know... > > > > 2. He also says that there's a "rule" that DDL should always be executed > > in exclusive connection. Where is this rule documented, if it exists? > > > > It would seem odd to ignore the drop table problem and also not document > > that it exists and that DDL should be executed in exclusive connection. > > In fact, if DDL is supposed to be executed only in exclusive connection, > > the engine should refuse to execute DDL in any non-exclusive connection > > and return a suitable error. > > > > If there's already an issue in the tracker about this, I'd appreciate a > > pointer to it so I at least would be able to follow it.
I fully agree. If DDL statements on an active database may result in corruption, then the Firebird engine should reject such requests or fix bugs in that area. -- With regards, Thomas Steinmaurer http://www.upscene.com/ Professional Tools and Services for Firebird FB TraceManager, IB LogManager, Database Health Check, Tuning etc.
