Changing the state of a database trigger of type "On Commit" from inactive to
active, the state change has no effect on other already opened connections.
Adding the ability to trace (using fbtrace) server access to system tables
--
Key: CORE-6020
URL: http://tracker.firebirdsql.org/browse/CORE-6020
Project: Firebird Core
On 3/1/19 4:50 PM, Dmitry Yemanov wrote:
01.03.2019 16:40, Adriano dos Santos Fernandes wrote:
BTW it would be good to known if this pull request (with
fb_info_tra_snapshot_number, SET TRANSACTION
SNAPSHOT [ AT NUMBER ] and isc_tpb_at_snapshot_number) will go to
master/v4.
No problems from
Wire compression not working without MSVC 2010 runtime installation (FB4 Beta1)
---
Key: CORE-6019
URL: http://tracker.firebirdsql.org/browse/CORE-6019
Project: Firebird Core
Make it possible to start multiple transactions (possibly in different
attachments) using the same initial transaction snapshot
---
Key: CORE-6018
Rename RDB$GET_CONTEXT('SYSTEM', 'SNAPSHOT_CN') to RDB$GET_CONTEXT('SYSTEM',
'SNAPSHOT_NUMBER')
---
Key: CORE-6016
URL: http://tracker.firebirdsql.org/browse/CORE-6016
Add transaction info fb_info_tra_snapshot_number
Key: CORE-6017
URL: http://tracker.firebirdsql.org/browse/CORE-6017
Project: Firebird Core
Issue Type: Improvement
Components:
01.03.2019 16:40, Adriano dos Santos Fernandes wrote:
BTW it would be good to known if this pull request (with
fb_info_tra_snapshot_number, SET TRANSACTION
SNAPSHOT [ AT NUMBER ] and isc_tpb_at_snapshot_number) will go to
master/v4.
No problems from me.
Dmitry
Firebird-Devel mailing
01.03.2019 15:40, Adriano dos Santos Fernandes wrote:
On 01/03/2019 10:28, Vlad Khorsun wrote:
...
BTW, what branch go you mean ?
https://github.com/FirebirdSQL/firebird/pull/193
I'll change SNAPSHOT_CN name in different commit as it's already present
in master.
Understand now
BTW
On 01/03/2019 10:28, Vlad Khorsun wrote:
> 01.03.2019 13:16, Adriano dos Santos Fernandes wrote:
>
>> I am assuming nobody objects and will implement the changes in the
>> branch.
>
> No objection, just not forget to change syntax\constant names as was
> agreed recently:
>
> ---
> Which then I
On 25/02/2019 13:21, Adriano dos Santos Fernandes wrote:
> Vlad is proposing the new info code to be named
> fb_info_tra_snapshot_number. I have no problem with it, provided that
> SNAPSHOT_CN is also renamed (with he seems to be open), but for what?
> SNAPSHOT_NUMBER too? (I have no problem with
I am just wondering if the requested feature is not already present.
A quick test with isc_database_info, with SYSDBA and a normal user
logged in shows:
- SYSDBA connection: only SYSDBA appears to be returned.
- User connection: only user name is returned.
From the security viewpoint, only
On 01/03/2019 07:43, Dimitry Sibiryakov wrote:
> 01.03.2019 11:32, Alex Peshkoff via Firebird-devel wrote:
>> But if one writes some funny plugin which generates random names in
>> authentication block - definitely yes :)
>
> They don't need to be random. I can imagine cases when they are a)
>
01.03.2019 11:32, Alex Peshkoff via Firebird-devel wrote:
But if one writes some funny plugin which generates random names in authentication block -
definitely yes :)
They don't need to be random. I can imagine cases when they are a) tied to a current
node in a cluster because Firebird
On 3/1/19 1:25 PM, Dimitry Sibiryakov wrote:
01.03.2019 8:59, Alex Peshkoff via Firebird-devel wrote:
Mapped user name has nothing to do with connection pool.
Are you sure that there will be never a case when single client-side
user name is mapped to different server-side users depending
01.03.2019 8:59, Alex Peshkoff via Firebird-devel wrote:
Mapped user name has nothing to do with connection pool.
Are you sure that there will be never a case when single client-side user name is
mapped to different server-side users depending on some conditions unknown to client?
--
Segfault when using expression index with complex expression
Key: CORE-6015
URL: http://tracker.firebirdsql.org/browse/CORE-6015
Project: Firebird Core
Issue Type: Bug
Affects
17 matches
Mail list logo
