Think again about CRUDv

[JC5]

Alright the CRUDv thing I thought of might not work, because even though CUDv is OK, the R for read isn't. The problem is that every model has different read-actions. All accounts, all accounts by a certain account_type, all budgets by a date limit which is inside a repetition.. bla bla bla.

So, I was thinking about multiple interfaces for sure, where a class might implement CUDv (not a good name but OK), and specialized Account / Budget interfaces that provide the methods required. Or maybe even something with traits and functions and so on; it's just that I don't know exactly how that works. Yet.

[JC5]

Alright let's start with a basic CUD interface and a validation interface.

[JC5]

Validation is now semi-ok, I'm going to wait for Laravel5 to come out and then we can rebuild it all anyway.