Versions Compared

Old Version 17

changes.mady.by.user Bartosz Palak

Saved on

compared with

New Version 18

changes.mady.by.user Bartosz Palak

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Warning

To be backward compatible or not to be backward compatible, that is the question!

Backward compatibility, understood as possibility of using 'old' and 'new' approach at the same time:

(plus) Can be achieved without big effort, as content of IDS class will not change (a lot)

(plus) All 'old' scripts will work - no modifications needed →  users are happy (smile)

(minus) Currently all methods use context kept in IDS that was a reason of many problems. New API is designed to overcome this issue. Keeping compatibility means that methods still have to be able to use context stored in IDS that is error prone.

(minus) All unwanted, messy methods operating on context stored (setCtx, etc)  must be kept 


...

Code Block
def put(self, occurrence=0, db_entry=None):

def get(self, occurrence=0, db_entry=None):

def putSlice(self, occurrence=0, db_entry=None):

def getSlice(self, time_requested, interpolation_method, occurrence=0, db_entry=None):

Additional methods

Code Block
def copy_values(self, ids):

def delete_data(self, occurrence=0, db_entry=None ):

def partial_get(self, dataPath, occurrence=0, db_entry=None):

def get_field(self, dataPath, occurrence=0, db_entry=None):


"Messy" methods

... that are not in line with proposed design but they must be kept to ensure backward compatibility.

Code Block
def setPulseCtx(self, ctx):
def getPulseCtx(self):