Thread: Open Source External-Database Connection Conventions
View Single Post
code177
2009-09-28 , 19:45
Guest | Posts: n/a | Thanked: 0 times | Joined on
#3
Originally Posted by zerojay View Post
What exactly are you working on here? It's hard to give you advice without more context.

You could always just create a new user/table per app user, I suppose and restrict access so that only the user can affect data in his table.
Let's say profile information as an example. Say you have a table with id, username, email, status, message, etc. You need to be able to insert and update, rows to this.

If it were just required to read information this would be easy, as you could just set the db permissions to read only. This falls apart when you need to insert and update though.

Perhaps a binary API? Does that break the "philosophy" of open source though? I guess if you released the binary's src files, but without any of the sensitive information it would be ok..