I have also been having problems with the use of the TIME WITH TIME ZONE
type and have been holding back on posting on the issue until I came up
with a suitable proposal. I wrote down my thoughts on the issue a few
weeks ago and have appended them to the end of this EMail - at the time
of writi
Hello,
I have made small changes to jrt\cvt.cpp and common\cvt.cpp to correct the
behavior of varchars not enforcing size limits when there are trailing
spaces in the string and uses UTF-8 in FB 3.0 and 4.0.
I would be very happy to share the changes if someone can take a look. It
behaves correc
fbsvcmgr can not decode information buffer returned by gfix list limbo service
--
Key: CORE-6309
URL: http://tracker.firebirdsql.org/browse/CORE-6309
Project: Firebird Core
On 2020-05-18 13:31, Adriano dos Santos Fernandes wrote:
Do you have an alternative (that do not broke things), better than use
fixed date (as Oracle does with 0001-01-01 and it even more broke
behavior) or a recent date?
Telling true I have bug desire to answer that error 'Invalid
operation' s
On 18/05/2020 04:00, Alex Peshkoff via Firebird-devel wrote:
> On 2020-05-16 05:22, Adriano dos Santos Fernandes wrote:
>> On 15/05/2020 12:46, Mark Rotteveel wrote:
>>> The decision to use 2020-01-01 as date for some of the time with time
>>> zone conversion leads to, in my opinion, confusing beha
On 2020-05-16 05:22, Adriano dos Santos Fernandes wrote:
On 15/05/2020 12:46, Mark Rotteveel wrote:
The decision to use 2020-01-01 as date for some of the time with time
zone conversion leads to, in my opinion, confusing behaviour:
select
time'13:25:32.1235 Europe/Amsterdam' at time zone 'ut
