i would expect the write and delete methods being called by generic code not knowing or caring about the optional flush parameter. i would propose we have a global config option on this class whether to autoflush (expected gaufrette behaviour) or not and expose some sort of getObjectManager method so that the user can flush it if needed. such as a method `setAutoFlush(boolean)`