Ignore:
Timestamp:
10/07/12 15:15:27 (8 years ago)
Author:
mnagni
Message:

Complete - # 22489: CEDA Observation Collection - phenomenonTime
 http://team.ceda.ac.uk/trac/ceda/ticket/22489
Complete - # 22518: The description is broken
 http://team.ceda.ac.uk/trac/ceda/ticket/22518
Complete - # 22488: CEDA Observation Collection - Geographical Extent
 http://team.ceda.ac.uk/trac/ceda/ticket/22488

Now the Moles3EPB explicitly call the "synchronise" method in the SQLAlchemy mapped classes to assure the persistence of the data
Uses the CedaMolesModel? v 0.1.5 which correct a major problem in synchronise the instances with database

File:
1 edited

Legend:

Unmodified
Added
Removed
  • mauRepo/MolesManager/trunk/src/libs/migration/MigrationEPB.py

    r8433 r8460  
    3232    def close(self): 
    3333        return self._session.close() 
     34             
     35    def persistInstance(self, instance): 
     36        """ 
     37            Adds a new migration object. 
     38            @param migrationObj: the migration object to add 
     39            @param session: an SQLAlchemy Session object. If None (default) the method creates 
     40            @return an updated, session independent, object instance reflecting the new persisted object  
     41        """       
     42        EPB.persistInstance(instance, self._session) 
     43        #return ret 
    3444 
    3545    def getAllDeploymentsMigrationByDataEntitySortedByDate(self, dataEntity, deploymentNames): 
Note: See TracChangeset for help on using the changeset viewer.