> -----Original Message----- > From: Alex Peshkoff [mailto:[email protected]] > Sent: Viernes, 06 de Abril de 2012 6:58 > > I agree here - not good. Currently we have to keep V4 flag in various > forms just to convert datetime_to_text() in different manner. > Only if we > decide to have separate BLR6 parser...
I just need a small class to read and write StreamType (I defined it) from a v4 or v5 BLR string. For v4, I would override those functions to read/write just one byte. Considering that now, few and very limited places are affected, having a separate BLR6 parser is unjustified. Using this helper class is what I would like to try to implement. What I have is my new type StreamType is all places I could find. I haven't touched the BLR generation and I haven't raised the BLR level (the engine performs same as before, but keeping the stream values in bigger vars, as Dmitry wanted). I'm ready to commit as I can't see a big bug caused by the change. The discussion on how to handle different BLR levels can continue (I have nothing to defend, because I don't have work done yet). C. ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
