Firebird 3.0.7 (x64) Installer is missing the employee.fdb database
---
Key: CORE-6424
URL: http://tracker.firebirdsql.org/browse/CORE-6424
Project: Firebird Core
Issue Type: Bu
20.10.2020 15:29, Alex Peshkoff via Firebird-devel wrote:
I see no difference.
Ah, ok. Perhaps I got fooled by brute force protection that delay every third
authentication attempt.
--
WBR, SD.
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/f
On 10/19/20 8:57 PM, Dimitry Sibiryakov wrote:
19.10.2020 19:09, Dimitry Sibiryakov wrote:
the time between the command has been issued and the error is shown.
And if you didn't notice: firebird.conf is default which means that
legacy auth is disabled on server side. I though that in this c
вт, 20 окт. 2020 г. в 14:43, Dmitry Yemanov :
>
> 20.10.2020 13:58, Vlad Khorsun via Firebird-devel wrote:
>
> >> AFAIU, it was discussed here in February 2018, thread "Valid date or
> >> not".
> >
> > I've re-read that thread quickly and I saw nor final decision, nor
> > proposition
> > to change
On 20-10-2020 12:40, Roman Simakov wrote:
вт, 20 окт. 2020 г. в 13:28, Mark Rotteveel :
Because documentantion here
(https://firebirdsql.org/en/firebird-date-literals/) says they are valid
separators.
Keep in mind, that link is an excerpt from Helen Borrie's Firebird Book
from 2004 (Firebird 1
20.10.2020 13:58, Vlad Khorsun via Firebird-devel wrote:
AFAIU, it was discussed here in February 2018, thread "Valid date or
not".
I've re-read that thread quickly and I saw nor final decision, nor
proposition
to change (or break) rules for traditional (legacy) date\time types
(without TZ).
19.10.2020 12:42, marius adrian popa wrote:
From pg release notes
https://www.postgresql.org/about/news/postgresql-13-released-2077/
https://www.postgresql.org/docs/13/btree-implementation.html#BTREE-DEDUPLICATION
ps: I don't know if Firebird can be optimized in a similar
AFAIU, PG tried to
вт, 20 окт. 2020 г. в 14:15, Vlad Khorsun via Firebird-devel
:
>I've re-read that thread quickly and I saw nor final decision, nor
> proposition
> to change (or break) rules for traditional (legacy) date\time types (without
> TZ).
Me too. Generally that discussion was focused on other format
20.10.2020 13:43, Dmitry Yemanov wrote:
20.10.2020 13:40, Roman Simakov wrote:
Because documentantion here
(https://firebirdsql.org/en/firebird-date-literals/) says they are valid
separators.
Keep in mind, that link is an excerpt from Helen Borrie's Firebird Book
from 2004 (Firebird 1.5 era)
20.10.2020 13:40, Roman Simakov wrote:
Because documentantion here
(https://firebirdsql.org/en/firebird-date-literals/) says they are valid
separators.
Keep in mind, that link is an excerpt from Helen Borrie's Firebird Book
from 2004 (Firebird 1.5 era). It is descriptive of what worked at the
вт, 20 окт. 2020 г. в 13:28, Mark Rotteveel :
> > Because documentantion here
> > (https://firebirdsql.org/en/firebird-date-literals/) says they are valid
> > separators.
>
> Keep in mind, that link is an excerpt from Helen Borrie's Firebird Book
> from 2004 (Firebird 1.5 era). It is descriptive of
On 20-10-2020 11:51, Dmitry Starodubov wrote:
Some string to date conversions that work in FB3 fail with an error in FB4:
SELECT cast('01 jan 1900' as timestamp) FROM rdb$database;
Statement failed, SQLSTATE = 22018
conversion error from string "01 jan 1900"
SELECT cast('01,jan,1900' as times
Hello.
Some string to date conversions that work in FB3 fail with an error in FB4:
SELECT cast('01 jan 1900' as timestamp) FROM rdb$database;
Statement failed, SQLSTATE = 22018
conversion error from string "01 jan 1900"
SELECT cast('01,jan,1900' as timestamp) FROM rdb$database;
Statement fai
Provide ability to specify file to fetch password when use CONNECT command in
SQL scenario
--
Key: CORE-6423
URL: http://tracker.firebirdsql.org/browse/CORE-6423
14 matches
Mail list logo
