Hello. Prior to sqlalchemy 0.7.6, we implemented our own mappers to override the _save_obj and _delete_obj methods.
Those methods don't exist anymore, and instead this responsibility is transfered to the persistence module. A little bit of context: We are using postgresql foreign tables, which are read only. So, the purpose of these custom mappers was to prevent insert/update/delete statements from going to the database, and instead save the mapped entities in their respective storages. Is there a way to achieve the same goal with the new architecture ? By the way, is there a documentation for the internals of the new architecture ? Thank you. -- Ronan Dunklau -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
