> 03.10.2014 21:20, Martijn Tonies (Upscene Productions) wrote: > >> I get exactly what's happening. >> >> And it's clear to me -something- has changed in this regard, cause if it >> weren't, everything would be just fine. > > Then tell us how a properly written application (the one not ignoring > the NULL indicator) could be affected by this "change". Something > working "just fine" does not mean it working correctly. > > P.S. This discussion is purely theoretical as compatibility has already > been restored in the meantime.
Thanks! We are all spending time to give Firebird 3 a test-drive and simply communicate when something weird/unknown happens to get some sort of confirmation if end-users (developers) are doing something wrong or if there might be a problem in Firebird. Nobody is perfect. ;-) Thanks again, Thomas ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
