09.03.2016 19:34, Jim Starkey wrote: > Is there a plan to phase out BLR?
Nothing specific yet. > Given that the next version of Firebird is likely to take a decade > anyway, why not start the discussion and planning now? We hope to have it released much sooner, sorry. That said, I have no problems to start the discussion now. Thinking about this, I see two good things: (1) we have SQL internally supported by the engine and (2) our node classes are somewhat prepared to work without the genBlr/parse steps (not immediately, but it's doable). Rewriting all GDML into SQL can surely be accomplished. We don't have SQL/GDML sources for many system triggers, just the byte-code. They could be reverse engineered, but I'd rather throw away system triggers at all and embed their functionality directly into the engine. The same for implicitly created triggers like CHECK constraints, etc. I'm not that happy to parse stored PSQL objects from SQL when loading them, parsing from BLR is way faster. And of course, databases with wiped out sources cannot be supported anymore. But we wanted to offer some alternative protection feature anyway. Dmitry ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
