On 24/03/17 15:12, Adriano dos Santos Fernandes wrote: >> Current implementation >> changed well known old behaviour not claiming it as a bug. I'd say it looks >> like >> a bug itself. >> > Changed a bugged design/implementation since 2009. Looks a bit late to > say this.
I'm still running FB1.5 on some legacy sites, so keeping up with all this new stuff is a problem. My FB3 installs simply did not work and I don't have time to find out why, but the ONE thing I expect to be consistent is that the data returned in a record is actually what is stored IN that record. The IDEA that a field that can store NULL but not actually return that in the result set is most definitely a bug. If you want to ensure a real value is returned, then the field should be NOT NULL and then the value stored is a real value that is only changed by a real UPDATE of some type. Certainly if a default value is a time stamp then it is no different to a fixed default value once a new record is added. -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk ------------------------------------------------------------------------------ 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
