AdapterInterface should reflect CRUD semantics

[codeliner]

Hi,

I'm looking for a flexible zf2 CRUD module for RAD prototyping. Your module seems to be a perfect candidate for the job. I love the seperation of entity and model definition and the CrudManager with it's related sub managers.
I want to connect an EventStore with a CRUD-ish middleware via CQRS. A CqrsAdapter should delegate CreateEntity, UpdateEntity and RemoveEntity commands to a command bus and in the simplest case generic command handlers would handle them and pass them to event sourced entities. This is the theory, but I've a problem with the AdapterInterface. It looks like it is designed to support doctrine or an ORM in general. The CRUD information get lost cause the AdapterInterface only defines a persist method. Seperated create/insert and update methods would be helpful, otherwise I need to introduce an idntity map or ask my read model if it already knows the entity.

What do you think? Would it be ok to change it? I can do it and send you a pull request. Would be much faster than write my own module but maybe it is a BC break if other adapters exist outside your module.