-
Notifications
You must be signed in to change notification settings - Fork 2
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
Abstracted storage container interface. #11
Comments
Any progress on this? BTW, I integrated your library into PolyAuth -> https://github.com/Polycademy/PolyAuth/ |
Looks Great :) I've been a bit busy with other project things lately, ill try and get the branch completed and merged this weekend for you. |
Hey Leigh, any updates on this. I see a new branch for it, is it currently working for MySQL? Cause that's all that's required to allow new pull requests. |
Should be ready for testing now. |
Does pgsql have foreign keys? Because if it doesn't then the sql and adapter needs some modifications. |
Would it be possible to provide a storage container interface. So that way you don't need to enforce PDO or MySQL?
Although php_rbac uses foreign keys, I'm sure if there was a storage container interface, people could code up plugins to support different databases and even NoSQL.
All you need to do is explicitly state what is expected of the current query. Such as the object relationship to the classes. I noticed you mapped the stuff coming out of the db to your classes.
As for foreign key support, that could be done via, some sort of application based mapping. So if there was a way to explicitly state the expectations of the database query (what to drop or cascade), then people could write plugins supporting NoSQL or databases with no foreign key support.
The text was updated successfully, but these errors were encountered: