Project

General

Profile

Feature #4176

make certain metadata tables aware of live runtime state

Added by Eric Faulhaber almost 7 years ago. Updated about 4 years ago.

Status:
New
Priority:
Normal
Assignee:
Igor Skornyakov
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:

Related issues

Related to Database - Feature #3814: more schema metadata Closed
Related to Database - Feature #9623: honoring database users and database-defined access control New

History

#1 Updated by Eric Faulhaber almost 7 years ago

FWD's current implementation of the _db metadata table is static, holding only information discovered at conversion. Apparently, this table can be used at runtime to determine actively connected databases. To support this, we will need to rework the implementation to be "live", similar to the _lock and _connect tables.

#2 Updated by Eric Faulhaber almost 7 years ago

  • Subject changed from make _db metadata table aware of active connections to make certain metadata tables aware of live runtime state

Add to the list of metadata which must be made "live":

_file._can-create
_file._can-delete
_file._can-dump
_file._can-load
_file._can-read
_file._can-write

#3 Updated by Greg Shah over 6 years ago

#4 Updated by Greg Shah over 5 years ago

How much of this task is already complete from the work done in #3814?

#5 Updated by Eric Faulhaber about 4 years ago

Greg Shah wrote:

How much of this task is already complete from the work done in #3814?

It looks like none. I think in #3814 we just added static representations of all these fields, but they are not "live", like _lock, _connect, _usertablestat, etc.

#6 Updated by Eric Faulhaber about 4 years ago

  • Assignee set to Igor Skornyakov

#7 Updated by Greg Shah over 1 year ago

  • Related to Feature #9623: honoring database users and database-defined access control added

Also available in: Atom PDF