On 5-4-2013 17:42, Dimitry Sibiryakov wrote:
> 05.04.2013 17:34, Doug Chamberlin wrote:
>> I would implement it so that if a user does not have SELECT permission on a
>> field that any
>> mention of that field in a SELECT statement is an outright error for that
>> user. Just as if
>> the field di
06.04.2013 13:42, Mark Rotteveel wrote:
> The question is: if you don't have permissions for a column, are you
> allowed to know of its existence?
I suppose the answer is "yes". Simply because system tables are world
readable and this is unlikely to be changed in the foreseeable future.
Dmitry
Hello All,
I see that core developers started to discuss ruche features - hidden
fields, readable db_key.
Did I miss something - do we already have beta of Firebird 3? Or we
still not have even alpha?
Guys, let's CONCENTRATE on delivering Firebird 3 alpha, then beta, then
release candidate an
06.04.2013 13:32, supp...@ibknowledgebase.com wrote:
>
> I see that core developers started to discuss ruche features - hidden
> fields, readable db_key.
Discussion is far from implementation. These threads are collecting
opinions, nothing more.
Dmitry
06.04.2013 11:51, Dmitry Yemanov wrote:
> 06.04.2013 13:42, Mark Rotteveel wrote:
>
>> The question is: if you don't have permissions for a column, are you
>> allowed to know of its existence?
>
> I suppose the answer is "yes". Simply because system tables are world
> readable and this is unlikely
On 6-4-2013 12:24, Dimitry Sibiryakov wrote:
> 06.04.2013 11:51, Dmitry Yemanov wrote:
>> 06.04.2013 13:42, Mark Rotteveel wrote:
>>
>>> The question is: if you don't have permissions for a column, are you
>>> allowed to know of its existence?
>>
>> I suppose the answer is "yes". Simply because sys
>> I see that core developers started to discuss ruche features - hidden
>> fields, readable db_key.
DY> Discussion is far from implementation. These threads are collecting
DY> opinions, nothing more.
Even so, I have to agree with Alexey. This discussion seems to have
arrived in the wrong time.
Hi, All.
We investigate a problem with server hanging on backup on of our damaged
database with -g option when it try to chase a dead record version.
In VIO_chase_record_version:
if (!(rpb->rpb_flags & rpb_chained) && rpb->rpb_flags & rpb_gc_active)
{
if (!rpb->rpb_transaction_nr) {
On 06/04/13 10:42, Mark Rotteveel wrote:
> The question is: if you don't have permissions for a column, are you
> allowed to know of its existence?
Drifting a bit OT, but one filesystem I knew years ago used ACLs and
separated list and use permission. So if you had list permission you
could see i
Dmitry,
> True, db_keys from aggregate views are problematic, but not for simple
> > joined views.
>
> Correct and it hasn't changed. I just meant that the view's DBKEY is not
> something separate, it simply a concatenation of the individual tables
> DBKEYs. You cannot select from a joined view us
10 matches
Mail list logo
