Adriano,
> Also there are new expressions, LOCALTIME and LOCALTIMESTAMP with
> functionality equivalent to the Firebird's CURRENT_TIME and
> CURRENT_TIMESTAMP.
I'd like to suggest you name these LOCAL_TIME and LOCAL_TIMESTAMP (with
the underscore in the middle) to make them look more like their
C
On 02/05/2018 05:59, Stefan Heymann wrote:
> Adriano,
>
>> Also there are new expressions, LOCALTIME and LOCALTIMESTAMP with
>> functionality equivalent to the Firebird's CURRENT_TIME and
>> CURRENT_TIMESTAMP.
> I'd like to suggest you name these LOCAL_TIME and LOCAL_TIMESTAMP (with
> the underscor
Just for thinking...
Can we create dialect 4 without old and strange things from sql standard?
Strange things are:
- inconsistances in naming such as CURRENT_TIMESTAMP and LOCALTIMESTAMP
- 'ABC' = 'ABC' -- ignored trailing spaces in varchars coparison (so we
can't have 'ABC' and 'ABC
Hi!
Time zones branch is almost feature complete.
There is two important subjects left:
- ICU in Windows - as I already said, it need to be upgraded and I would
like it builded as the upstream does, i.e., with full data. It would be
good if someone volunter to do it as I do not have nor even kno
On 30-4-2018 04:50, Adriano dos Santos Fernandes wrote:
So before migrate to v4, users can adjust their code using Firebird 3
and once upgraded there will be no problems.
I also want to repeat my opinion that I think it is a bit too late in
the Firebird 4 development to include this feature no
On 30-4-2018 09:52, fbbt wrote:
3. Maybe we need to put a sample of firebird.pas at github. It will allow other
developers to patch it in more productive way than now.
As I understand it, firebird.pas is generated by Cloop, so allowing
people to patch it would be against the intent. The probl
On 30-4-2018 04:50, Adriano dos Santos Fernandes wrote:
Time zones branch is almost feature complete.
There is two important subjects left:
- ICU in Windows - as I already said, it need to be upgraded and I would
like it builded as the upstream does, i.e., with full data. It would be
good if so
30.04.2018 4:50, Adriano dos Santos Fernandes wrote:
It was been created four new datatypes:
- TIME WITH TIME ZONE
- TIMESTAMP WITH TIME ZONE
Do these contain time/timestamp in UTC and time zone, or time/timestamp in local time
and time zone?
So the first compatibility problem is when cli
allow to specify subfolders when declare udr function
-
Key: CORE-5809
URL: http://tracker.firebirdsql.org/browse/CORE-5809
Project: Firebird Core
Issue Type: Improvement
Componen
On 29/04/18 21:47, Adriano dos Santos Fernandes wrote:
But standard CURRENT_TIME and CURRENT_TIMESTAMP works different than
Firebird, as they returns the "WITH TIME ZONE" types.
Tweaking CURRENT_TIME/CURRENT_TIMESTAMP for compatibility is problematic.
So how do I maintain a functional system
Hi Jorge. No i'm using the arm version. On a real device.
Could you share your code?
Thanks
Em Seg, 30 de abr de 2018 17:40, Jorge Gonçalves
escreveu:
>
>
> On Mon, Apr 30, 2018 at 12:08 PM Luiz Alberto Tessarolli <
> tessaro...@gmail.com> wrote:
>
>> Hi Jorge,
>>
>> Config.AppDir points to Appl
(resending as they haven't appeared on the list yet)
On 30-4-2018 04:50, Adriano dos Santos Fernandes wrote:
Time zones branch is almost feature complete.
There is two important subjects left:
- ICU in Windows - as I already said, it need to be upgraded and I would
like it builded as the upstr
30.04.2018 5:50, Adriano dos Santos Fernandes wrote:
Hi!
Time zones branch is almost feature complete.
There is two important subjects left:
- ICU in Windows - as I already said, it need to be upgraded and I would
like it builded as the upstream does, i.e., with full data. It would be
good if
01.05.2018 13:45, Vlad Khorsun wrote:
"Official" compiler for fb3 on Windows is (old) VC10. Snapshot builds of
both fb3 and fb4 uses VC12 (VS2013), iirc.
FB3 snapshots are built using VC10.
Dmitry
--
Check out the v
01.05.2018 16:19, Adriano dos Santos Fernandes wrote:
What should be used by default ?
It should match functionality and default of SET DECFLOAT, i.e., be
default the new behavior (describe types with TZ as types with TZ).
Problematic clients will use the legacy option.
How? Legacy appli
On 2-5-2018 10:59, Stefan Heymann wrote:
Adriano,
Also there are new expressions, LOCALTIME and LOCALTIMESTAMP with
functionality equivalent to the Firebird's CURRENT_TIME and
CURRENT_TIMESTAMP.
I'd like to suggest you name these LOCAL_TIME and LOCAL_TIMESTAMP (with
the underscore in the midd
1.
Place firebird.pas (for all FB releases) to official repository at GitHub.
This is a one of the first places where it is expected to be found.
2.
- firebird.pas for 3.0.0 is not the same as firebird.pas for 3.0.1
- firebird.pas for 3.0.1 is not the same as firebird.pas for 3.0.2
- firebird.pas
On 01/05/2018 11:30, Dimitry Sibiryakov wrote:
>
>
>> There is session time zone. Session time zone is currently defined as
>> default with the server time zone.
>>
>> We may think that's not ideal and session time zone should be defined
>> with the client time zone initially. But that per se is no
02.05.2018 20:20, Adriano dos Santos Fernandes wrote:
Client library can add a timezone item into DPB if it is not
provided by application, as it is done for application name now.
Midware can set this value to whatever they like.
Do not work that way.
Web applications and middlewares works
On 02/05/2018 13:16, Lester Caine wrote:
> On 29/04/18 21:47, Adriano dos Santos Fernandes wrote:
>> But standard CURRENT_TIME and CURRENT_TIMESTAMP works different than
>> Firebird, as they returns the "WITH TIME ZONE" types.
>>
>> Tweaking CURRENT_TIME/CURRENT_TIMESTAMP for compatibility is
>> p
On 02/05/18 20:22, Adriano dos Santos Fernandes wrote:
On 02/05/2018 13:16, Lester Caine wrote:
On 29/04/18 21:47, Adriano dos Santos Fernandes wrote:
But standard CURRENT_TIME and CURRENT_TIMESTAMP works different than
Firebird, as they returns the "WITH TIME ZONE" types.
Tweaking CURRENT_TI
21 matches
Mail list logo
