24.10.2018 09:08, liviuslivius wrote:
today's snapshot of FB3 is missing
Uploaded now, thanks.
Dmitry
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
The source code cited below clearly tells the root of the problem that I
reported.
The problem should be resolved by setting sortCollator's UCOL_STRENGTH
property as well as compareCollator.
There are two collater objects relating to this problem; Those are
sortCollator(*A) and compareCollato
Hi,today's snapshot of FB3 is missing regards,Karol BieniaszewskiFirebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
On 23/10/2018 15:43, Adriano dos Santos Fernandes wrote:
AFAIK, but I may be wrong, "TIMESTAMP" is not a correct single word too.
There has been a similar debate over TIME ZONE and the RFC for tzdist
specifically adopted TIMEZONE to get around the need for an underscore.
TIMESTAMP became the
On 23-10-2018 16:43, Adriano dos Santos Fernandes wrote:
AFAIK, but I may be wrong, "TIMESTAMP" is not a correct single word too. :)
Well: https://dictionary.cambridge.org/us/dictionary/english/timestamp
(although other dictionaries only list time stamp)
It seems in English, use of time stam
On 23/10/2018 11:36, Mark Rotteveel wrote:
> On 23-10-2018 16:20, liviuslivius wrote:
>> Really strange "standard" here...
>
> Standards are nothing but inconsistent, especially as they evolve over
> time. However, CURRENT_TIME dates back to at least the SQL:92 standard
> (and probably existed earl
On 23-10-2018 16:20, liviuslivius wrote:
Really strange "standard" here...
Standards are nothing but inconsistent, especially as they evolve over
time. However, CURRENT_TIME dates back to at least the SQL:92 standard
(and probably existed earlier in some form in non-standardized
dialects), w
Really strange "standard" here...Thank youRegards,Karol Bieniaszewski
nullFirebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
On 23-10-2018 11:36, liviuslivius wrote:
Hi,
why "LOCALTIMESTAMP" not "LOCAL_TIMESTAMP" as is for
e.g. "CURRENT_TIMESTAMP"?
That is because SQL:2016, ISO 9075-2:2016, in section 6.36 value function>, specifies the names as CURRENT_TIME, CURRENT_TIMESTAMP
and LOCALTIME and LOCALTIMESTAMP .
M
23.10.2018 11:36, liviuslivius wrote:
why "LOCALTIMESTAMP" not "LOCAL_TIMESTAMP" as is for e.g. "CURRENT_TIMESTAMP"?
SQL standard.
--
WBR, SD.
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
Hi,
why "LOCALTIMESTAMP" not "LOCAL_TIMESTAMP" as is for e.g. "CURRENT_TIMESTAMP"?
regards,
Karol BieniaszewskiFirebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
2018. 10. 22. 17:31 keltezéssel, Dimitry Sibiryakov írta:
22.10.2018 17:28, Gabor Boros wrote:
How long distance is enough for the correct results?
Usually it is run for 2-3 hours at least.
The attached numbers come from 1 hour. I will try with 2 and 3 hours.
Gabor
Firebird-Devel mail
12 matches
Mail list logo