03.03.2017 13:53, Alex Peshkoff wrote:
> May be I was not enough precise - that's not big problem for major
> release (FB4), but not good for 3.0.2.
While i not agree re. "problem" for 3.0.2, i'm not going to insist.
Regards,
Vlad
On 03/03/17 14:48, Vlad Khorsun wrote:
> 03.03.2017 13:15, Alex Peshkoff wrote:
>> On 03/01/17 20:51, Vlad Khorsun wrote:
>>> 01.03.2017 19:22, Dmitry Yemanov wrote:
> 01.03.2017 19:50, Vlad Khorsun wrote:
>>> ..
> Also, I prefer to avoid to return as a string something that is not a
03.03.2017 12:48, Vlad Khorsun wrote:
>Should we never add new non-standard system functions because of this ?
May be you should give them RDB$ prefix.
--
WBR, SD.
--
Check out the vibrant tech community on
03.03.2017 13:15, Alex Peshkoff wrote:
> On 03/01/17 20:51, Vlad Khorsun wrote:
>> 01.03.2017 19:22, Dmitry Yemanov wrote:
01.03.2017 19:50, Vlad Khorsun wrote:
>> ..
Also, I prefer to avoid to return as a string something that is not a
string.
>>> Agreed here. From another side, I
On 03/01/17 20:51, Vlad Khorsun wrote:
> 01.03.2017 19:22, Dmitry Yemanov wrote:
>>> 01.03.2017 19:50, Vlad Khorsun wrote:
> ..
>>> Also, I prefer to avoid to return as a string something that is not a
>>> string.
>> Agreed here. From another side, I don't like polluting the global
>> namespace
01.03.2017 19:22, Dmitry Yemanov wrote:
>> 01.03.2017 19:50, Vlad Khorsun wrote:
..
>> Also, I prefer to avoid to return as a string something that is not a string.
>
> Agreed here. From another side, I don't like polluting the global
> namespace with non-standard but reserved keywords.
Same
01.03.2017 19:50, Vlad Khorsun wrote:
>
>>> If this variable is added as a context variable into "SYSTEM" namespace,
>>> simple
>>> "START_TIMESTAMP" should be enough
>>
>> It could be confused with attachment-start timestamp.
>
> I thought it is clear that ticket is about new system contex
01.03.2017 17:38, Dmitry Yemanov wrote:
> It could be confused with attachment-start timestamp.
Add both. ;-)
--
WBR, SD.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites,
01.03.2017 19:33, Dimitry Sibiryakov wrote:
> If this variable is added as a context variable into "SYSTEM" namespace,
> simple
> "START_TIMESTAMP" should be enough
It could be confused with attachment-start timestamp.
Dmitry
01.03.2017 17:24, Vlad Khorsun wrote:
> As for the name, i prefer CURRENT_TRANSACTION_TIME or
> CURRENT_TRANSACTION_TIMESTAMP.
If this variable is added as a context variable into "SYSTEM" namespace,
simple
"START_TIMESTAMP" should be enough, as none of transaction-related variables
there
01.03.2017 17:24, Vlad Khorsun wrote:
>Is there any objection to add it into upcoming v3.0.2 and v4 ?
3.0 is supposed to be a feature-stable branch.
--
WBR, SD.
--
Check out the vibrant tech community on one
01.03.2017 9:33, Karol Bieniaszewski (JIRA) wrote:
> Add context variable about transaction start timestamp
> --
>
> Key: CORE-5493
> URL: http://tracker.firebirdsql.org/browse/CORE-5493
> Project:
Add context variable about transaction start timestamp
--
Key: CORE-5493
URL: http://tracker.firebirdsql.org/browse/CORE-5493
Project: Firebird Core
Issue Type: New Feature
13 matches
Mail list logo
