Package gavo :: Package rsc :: Module metatable :: Class MetaTableHandler
[frames] | no frames]

Class MetaTableHandler

source code

object --+
         |
        MetaTableHandler

an interface to DaCHS meta tables.

This used to be a fairly complex interface to all sorts for DC-related metadata. These day, the only thing it does is figure out where table definitions reside and which are available for ADQL. This thing has been a bad idea all around.

Though you can construct MetaTableHandlers of your own, you should use base.caches.getMTH(None) when reading.

Instance Methods
 
__init__(self)
x.__init__(...) initializes x; see help(type(x)) for signature
source code
 
close(self) source code
 
reset(self) source code
 
getTableDefForTable(self, *args, **kwargs)
returns a TableDef for tableName.
source code
 
getTAPTables(self, *args, **kwargs)
returns a list of all names of tables accessible through TAP in this data center.
source code

Inherited from object: __delattr__, __format__, __getattribute__, __hash__, __new__, __reduce__, __reduce_ex__, __repr__, __setattr__, __sizeof__, __str__, __subclasshook__

Properties

Inherited from object: __class__

Method Details

__init__(self)
(Constructor)

source code 

x.__init__(...) initializes x; see help(type(x)) for signature

Overrides: object.__init__
(inherited documentation)

getTableDefForTable(self, *args, **kwargs)

source code 

returns a TableDef for tableName.

As it is not a priori clear which RD a given table lives in, this goes through dc.tablemeta to figure this out. The object comes from the actual RD, though, so this might very well trigger database action and RD loading.

Decorators:
  • @_retryProtect

getTAPTables(self, *args, **kwargs)

source code 

returns a list of all names of tables accessible through TAP in this data center.

Decorators:
  • @_retryProtect