...

...

 DB_ENTRY

Class structure:

Class keeps information about one, particular  database entry (eg. pulse-file, HDC container, SQL-database, etc etc)

Class structure:

• db_entry class represents data accessible through Access Layer 
• hdc_entry , sql_entry  are examples of classes that represents IMAS data entry accessible via other mechanisms than AL (if they will be implemented in future)
• imas_entry a parent class for all ??_entry classes. It will be implemented in future if any other mechanism of accessing data than AL will be used. Could be empty...  

THIS PAGE FOCUSES ON DESIGN OF DB_ENTRY AND IDS CLASSES ONLY!, DB_ENTRY - any better names?

Definition (constructor)

DB Entry  is defined by:

• backend
• user name (eg. g2bpalak )
• db name (eg. test )
• data version - do we need it (see Open Points)?
• shot
• run
• _id - MDSPLUS_BACKEND, MEMORY_BACKEND, ASCII_BACKEND - mandatory -   
• db name - eg. test   - mandatory 
• shot - mandatory
• run - mandatory
• user name - eg. g2bpalak  -  optional - if None → $USER
• data version - e.g. 3 - optional - currently not used,  we should keep it as it will point us to a proper dir in imasdb structure, when we develop versions 4,5, etc  - if None → 3

def __init__(self, backendIDbackend_id, db_name, shot, run, user_name userName= None, data_version = 3)
	if userName is None:
		user = $USER

...

Additional "URI-based" constructor will be added in future...

...

...

.

...

Create/open/close

All parameters that defines db_entry  are set in constructor, so create, open, close will have no arguments

def create(self, options = None)
def open(self, options = None)
def close(self)

, options = None)

options - additional options (possibly backend specific)

Put/Get IDS

def get(self, idsName, occurrence = 0) # idsName (e.g. 'equilibrium')
	return ids

...