On 2019-12-26 18:43, Mark Rotteveel wrote:
128-bit literal - is it Numeric or Decimal?
Given the lack of an int128, we should consider it an exact numeric
literal of either DECIMAL or NUMERIC. The standard says (5.3 ):
"""
22) The declared type of an ENL is an
implementation-defined exac
On 2019-12-26 19:01, Mark Rotteveel wrote:
On 26/12/2019 16:43, Mark Rotteveel wrote:
Formally, I take this to mean we should choose one type, eg DECIMAL,
but that would probably not match people assuming that literal
without decimal points are integral literals.
We could consider a middle g
On 26/12/2019 16:43, Mark Rotteveel wrote:
Formally, I take this to mean we should choose one type, eg DECIMAL, but
that would probably not match people assuming that literal without
decimal points are integral literals.
We could consider a middle ground where literals without decimal point
On 26/12/2019 16:11, Alex Peshkoff via Firebird-devel wrote:
On 2019-12-26 17:40, Mark Rotteveel wrote:
On 25/12/2019 12:11, Alex Peshkoff via Firebird-devel wrote:
On 2019-12-11 18:06, Mark Rotteveel wrote:
In other words, it looks like the mapping:
of INTEGER-backed types
1. ignores s
On 2019-12-26 17:40, Mark Rotteveel wrote:
On 25/12/2019 12:11, Alex Peshkoff via Firebird-devel wrote:
On 2019-12-11 18:06, Mark Rotteveel wrote:
In other words, it looks like the mapping:
of INTEGER-backed types
1. ignores subtype information and
Ignoring subtype is as designed here.
On 25/12/2019 12:11, Alex Peshkoff via Firebird-devel wrote:
On 2019-12-11 18:06, Mark Rotteveel wrote:
In other words, it looks like the mapping:
of INTEGER-backed types
1. ignores subtype information and
Ignoring subtype is as designed here. The aim of SET BIND is to help
client deal
On 2019-12-11 18:06, Mark Rotteveel wrote:
In other words, it looks like the mapping:
of INTEGER-backed types
1. ignores subtype information and
Ignoring subtype is as designed here. The aim of SET BIND is to help
client deal with fields values in cases when it for some reason can not
