Hi!
As I stated previously in this thread, IN/ANY/ALL and its negated form
works only in simple (existent before the boolean data type was
introduced) expressions.
That happens because Firebird returns FALSE for some queries that should
return NULL.
There is special handling for NOT (IN/ANY/ALL
File-system ID may be duplicated among databases located on different volumes
-
Key: CORE-6323
URL: http://tracker.firebirdsql.org/browse/CORE-6323
Project: Firebird Core
On 03/06/2020 12:58, Mark Rotteveel wrote:
That is what you can expect when linking to documentation on a branch
called 'work' (which, afaik, was deleted a very long time ago), which
implies it's transient.
It had been used in relation to a previous thread and was the only link
I could see
On 2020-06-03 12:51, Lester Caine wrote:
On 03/06/2020 09:24, Alex Peshkoff via Firebird-devel wrote:
Has
https://github.com/FirebirdSQL/firebird/blob/work/time-zone-support/doc/sql.extensions/README.time_zone.md
Been replaced with something more up to date?
On 2020-06-02 23:32, Adriano dos Santos Fernandes wrote:
On 02/06/2020 16:45, Mark Rotteveel wrote:
Documentation should be improved for this case too.
This essentially means that
select * from atable where sometimecolumn > current_time;
will yield different results when the time zone is
On 03/06/2020 09:24, Alex Peshkoff via Firebird-devel wrote:
Has
https://github.com/FirebirdSQL/firebird/blob/work/time-zone-support/doc/sql.extensions/README.time_zone.md
Been replaced with something more up to date?
On 03/06/2020 04:10, Alex Peshkoff via Firebird-devel wrote:
> On 2020-06-03 00:17, Dimitry Sibiryakov wrote:
>> 02.06.2020 21:45, Mark Rotteveel wrote:
>>> I think that is extremely confusing, and not acceptable.
>>
>> That's why everyone was given several years to replace CURRENT_TIME
>> with
On 2020-06-03 10:56, Lester Caine wrote:
On 03/06/2020 08:23, Lester Caine wrote:
On 02/06/2020 22:17, Dimitry Sibiryakov wrote:
02.06.2020 21:45, Mark Rotteveel wrote:
I think that is extremely confusing, and not acceptable.
That's why everyone was given several years to replace
On 03/06/2020 08:23, Lester Caine wrote:
On 02/06/2020 22:17, Dimitry Sibiryakov wrote:
02.06.2020 21:45, Mark Rotteveel wrote:
I think that is extremely confusing, and not acceptable.
That's why everyone was given several years to replace CURRENT_TIME
with LOCALTIME and don't use TIME
On 02/06/2020 22:17, Dimitry Sibiryakov wrote:
02.06.2020 21:45, Mark Rotteveel wrote:
I think that is extremely confusing, and not acceptable.
That's why everyone was given several years to replace CURRENT_TIME
with LOCALTIME and don't use TIME WITH TIMEZONE at all.
Has
On 2020-06-03 00:17, Dimitry Sibiryakov wrote:
02.06.2020 21:45, Mark Rotteveel wrote:
I think that is extremely confusing, and not acceptable.
That's why everyone was given several years to replace CURRENT_TIME
with LOCALTIME and don't use TIME WITH TIMEZONE at all.
Yes. What we
11 matches
Mail list logo
