As mentioned in #7 and #9, it would be helpful to implement a method that constructed an aospy core object from a DB object. This would allow, for instance, a user to potentially recover aospy objects that they deleted from their aospy_user directory. It could also allow us to write more complicated query functions above the backend level using some basic abstract querying building blocks. Finally, it would allow for an easy, consistent, way to return all metadata associated with an aospy DB object that resulted from a query.
This would require storing all constructor-required metadata from the aospy core objects in the DB. This is currently not done for simplicity, but should be possible in principle. For example the list of grid-files in the Model object will require a separate DB table, but this is just a simple one-to-many relationship that has been implemented multiple times already.
As mentioned in #7 and #9, it would be helpful to implement a method that constructed an aospy core object from a DB object. This would allow, for instance, a user to potentially recover aospy objects that they deleted from their
aospy_userdirectory. It could also allow us to write more complicated query functions above the backend level using some basic abstract querying building blocks. Finally, it would allow for an easy, consistent, way to return all metadata associated with an aospy DB object that resulted from a query.This would require storing all constructor-required metadata from the aospy core objects in the DB. This is currently not done for simplicity, but should be possible in principle. For example the list of grid-files in the
Modelobject will require a separate DB table, but this is just a simple one-to-many relationship that has been implemented multiple times already.