New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split midcom_baseclasses_core_dbobject #142

flack opened this Issue Jan 30, 2015 · 0 comments


None yet
1 participant

flack commented Jan 30, 2015

Reported by flack on 30 Apr 2029 07:50 UTC
ATM, almost DBA to database interactions are ultimately performed by one giant (~2000 lines) class of static methods. This should be split up into a sub-module where different actions (create/read/update/delete/parameters/etc., maybe even qb & mc) are implemented in different classes. This would not only make the DBa layer more maintainable, but it would also make it easier to implement alternative storage drivers (like, say, Doctrine/PHPCR or something else).


@flack flack self-assigned this Jan 30, 2015

@flack flack added this to the undecided milestone Jan 30, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment