-
Notifications
You must be signed in to change notification settings - Fork 1
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
Revise the Database #3
Comments
I thought about using a "dumb" database , that doesn't have validations (only standards like "NOT EMPTY"). All validation will done in the app, including data consistency. |
Well, This will use less data through the network and less database server's resources. I'm afraid this process result in invalid or bad data. |
@cfilipes But the validation exists... on the app... that validates all the info before INSERTs |
Yeah, but I'm thinking on a second or third party client communicanting with our db. |
@cfilipes In this case, the Core API validates information, no clients can access directly our DB |
Yep, just making it clear... |
Will be more easy for porting... and add new tables... ;) |
I make some adjustments on DB... |
Make a dumb db allows you to make heavy migration tasks without any problem. As Erik said, the database MUST be accessed through a core with the necessary validation. |
Make a revise of the first database schema...
vialerta_core_db.mwb.tar.gz
Open with MySQL Workbench
The text was updated successfully, but these errors were encountered: