To name a few things(i dont know how accurate they are, but these come into my mind):Please only drop the code that has an alternative in storage and is backwards compatible. I am still working on a version, which supports the features that are in the old database layer.I am curious to which features are missing in the new layer as we have migrated with close to no problems to it.
- Much harder to write a new version for a different database(doesnt look at the config directory but in resources, maybe this is a bug, but i dont understand why these files are now in the resources)
- Not backwards compatible with the older -support-classes- created databases (maybe no need, but it should be a good thing, that it could be configured that way by using a config file)
- View support
- Extending support
- Storage of bytes in database
- ...
I am not saying that we need all these functionality, but when we drop functionality, we have to know what we are removing.
Im willing to put time in this, but given my current work situation, i need some support to get all the stuff going in the storage layer.
