On 22-7-2019 11:18, Dmitry Yemanov wrote:
13.07.2019 12:10, Mark Rotteveel wrote:
I propose that for Firebird 4 we bring this inline with the standard:
1. Change and document FLOAT(p) to apply precision in binary digits,
that is:
- p in [1, 24] is a 32 bit single precision
- p in [25, 53]
On 2019-07-22 11:05, Alex Peshkoff via Firebird-devel wrote:
On 20.07.2019 10:54, Mark Rotteveel wrote:
Anyone?
Single question - does it add more conflicts to grammar?
It shouldn't, because it we already have this in the grammar, just not
documented and with non-standard meaning.
Mark
13.07.2019 12:10, Mark Rotteveel wrote:
I propose that for Firebird 4 we bring this inline with the standard:
1. Change and document FLOAT(p) to apply precision in binary digits,
that is:
- p in [1, 24] is a 32 bit single precision
- p in [25, 53] is a 64 bit double precision
- p < 1 and p >
On 20.07.2019 10:54, Mark Rotteveel wrote:
Anyone?
Single question - does it add more conflicts to grammar?
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
Anyone?
On 13-7-2019 11:10, Mark Rotteveel wrote:
Currently Firebird has two documented floating point datatypes:
- FLOAT (a 32 bit single precision)
- DOUBLE PRECISION (a 64 bit double precision)
Firebird also has the - undocumented - datatypes
- REAL (a 32 bit single precision), essentially
On 13-7-2019 11:10, Mark Rotteveel wrote:
I propose that for Firebird 4 we bring this inline with the standard:
1. Change and document FLOAT(p) to apply precision in binary digits,
that is:
- p in [1, 24] is a 32 bit single precision
- p in [25, 53] is a 64 bit double precision
- p < 1 and p
Currently Firebird has two documented floating point datatypes:
- FLOAT (a 32 bit single precision)
- DOUBLE PRECISION (a 64 bit double precision)
Firebird also has the - undocumented - datatypes
- REAL (a 32 bit single precision), essentially an alias for FLOAT. REAL
is a SQL standard type.
-
