Use Data Mapper model rather than up-side-down Active Record about sagepay HOT 1 OPEN

Here is a good (from what I can see, though I'm no expert) example of a data mapper:

https://github.com/iio/datamapper

Now, this also leads to another interesting idea. We have one big "Transaction" model at the moment that persists transactional data from one page to another. Depending on the action being performed, different fields need to be completed (are used or not used). Maybe instead of one Transaction model, we could use separate models - one for each service, or one for each message type. The model would tell the data mapper which fields to save and retrieve, so some (or all) of the central Transaction metadata would be moved out to the models. We would still need to find a way to define the storage structure (the table columns) which needs to be able to store any of the multiple models (or perhaps they could be stored in separate tables, if that is what the mapper adapter chooses to do.

from sagepay.