In Firebird 4 RC1 Round () does not round up more to decimal numbers
-
Key: CORE-6533
URL: http://tracker.firebirdsql.org/browse/CORE-6533
Project: Firebird Core
Issue Type
Results of сoncatenation with blob has no info about collation of source
columns (which are declared with such info)
Key: CORE-6532
URL: http://tr
COMPUTED BY column looses charset and collate of source field when is
either of type BLOB or VARCHAR casted to BLOB
---
Key: CORE-6531
URL: h
Hello,
Always build a string with four digits for year in dialect 1?
For me - it is OK :)
Regards,
Dmitry Kovalenko
пт, 2 апр. 2021 г. в 20:03, Adriano dos Santos Fernandes <
adrian...@gmail.com>:
> Hi!
>
> I'm not very aware on how timestamps were working in dialect 1.
>
> But for sure CORE-6
Hi!
I'm not very aware on how timestamps were working in dialect 1.
But for sure CORE-6494 shows some problems.
First in engine:
select cast(cast('2-DEC-0083' as timestamp) as varchar(64)) from
rdb$database;
Results in string '2-DEC-83'
Second in ISQL:
select cast('2-DEC-0083' as timestamp)
On 4/2/21 6:09 PM, Dimitry Sibiryakov wrote:
02.04.2021 15:19, Biswapriyo Nath wrote:
How can I fix the build?
In short - you cannot. It is my experience as a mingw build
maintaner before 15 years.
Not sure long term, may Dimitry is right. I did not support that build.
What about this p
02.04.2021 15:19, Biswapriyo Nath wrote:
How can I fix the build?
In short - you cannot. It is my experience as a mingw build maintaner before
15 years.
--
WBR, SD.
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
I am trying to build firebird with mingw toolchain. I have been fixing
some issues here[1]. But I have came across a blocking issue. After
building firebird.exe, the make wants to compile
utilities/guard/guard.cpp but it uses fork(2) which is not in
available in Win32 platform. How can I fix the bu
On 02/04/2021 08:12, Vlad Khorsun wrote:
> 02.04.2021 14:00, Adriano dos Santos Fernandes wrote:
>> Hi!
>>
>> Firebird is doing the difficult thing.
>>
>> It's good to store all metadata parts and even for extract it may be
>> useful.
>>
>> But we should also store routines header in addition and s
02.04.2021 14:00, Adriano dos Santos Fernandes wrote:
Hi!
Firebird is doing the difficult thing.
It's good to store all metadata parts and even for extract it may be useful.
But we should also store routines header in addition and separately from
the body.
Why separately ? Backward compati
Hi!
Firebird is doing the difficult thing.
It's good to store all metadata parts and even for extract it may be useful.
But we should also store routines header in addition and separately from
the body.
With routines header, extract would be much easier and will preserve
every comments and form
Comments to SP parameter (typed within SP header declaration) can be lost in
metadata extraction script (if parameter is declared *without* DEFAULT or "="
modifier)
12 matches
Mail list logo
