Ok, so we do not follow the standard in our currently implementation,
but we follow the standard in the DDL checking... this is a bit messy
[]s
Carlos
http://www.firebirdnews.org
FireBase - http://www.FireBase.com.br
DY> 10.08.2017 21:57, Carlos H. Cantu wrote:
>> DY> e.g. 1234567890.1234 is a
operating system directive MapViewOfFile failed access denied
-
Key: CORE-5594
URL: http://tracker.firebirdsql.org/browse/CORE-5594
Project: Firebird Core
Issue Type: Bug
Affect
10.08.2017 21:57, Carlos H. Cantu wrote:
DY> e.g. 1234567890.1234 is a valid (15, 4) but cannot be converted to (15, 6).
Are you sure? I can store such value both in (15, 4) as well in (15, 6).
Formally, it cannot be stored inside (15, 6). But historically, FB
ignores the declared precision
On 11-8-2017 11:29, Dimitry Sibiryakov wrote:
11.08.2017 11:21, Alex via Firebird-devel wrote:
BLOBs have hard-coded BPB which makes all BLOBs have stream type.
What is advantage of stream BLOBs?
You can seek stream blobs absolute (blb_seek_from_head), relative from
current position (blb
On 11.08.2017 12:29, Dimitry Sibiryakov wrote:
11.08.2017 11:21, Alex via Firebird-devel wrote:
BLOBs have hard-coded BPB which makes all BLOBs have stream type.
What is advantage of stream BLOBs?
No disadvantages :-)
Comments?
BPB is not only about BLOB type, but also for using b
11.08.2017 11:21, Alex via Firebird-devel wrote:
BLOBs have hard-coded BPB which makes all BLOBs have stream type.
What is advantage of stream BLOBs?
Comments?
BPB is not only about BLOB type, but also for using blob filters. Can your suggestion
handle cases when a table has two BLOB f
Currently implemented in batches
(https://github.com/FirebirdSQL/firebird/tree/batch) BLOBs have
hard-coded BPB which makes all BLOBs have stream type. Certainly this is
not what we want in release version. I suggest the following:
- current hard-coded BPB remains as default for all BLOBs crea
