Skip to content
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

Open
erikperin opened this issue Sep 19, 2016 · 9 comments
Open

Revise the Database #3

erikperin opened this issue Sep 19, 2016 · 9 comments

Comments

@erikperin
Copy link
Member

erikperin commented Sep 19, 2016

Make a revise of the first database schema...

vialerta_core_db.mwb.tar.gz

Open with MySQL Workbench

@erikperin
Copy link
Member Author

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.

@soumfilipe
Copy link

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.

@erikperin
Copy link
Member Author

@cfilipes But the validation exists... on the app... that validates all the info before INSERTs

@soumfilipe
Copy link

Yeah, but I'm thinking on a second or third party client communicanting with our db.

@erikperin
Copy link
Member Author

@cfilipes In this case, the Core API validates information, no clients can access directly our DB

@soumfilipe
Copy link

Yep, just making it clear...

@erikperin
Copy link
Member Author

Will be more easy for porting... and add new tables... ;)

@erikperin
Copy link
Member Author

I make some adjustments on DB...

@EltonCarreiro
Copy link

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.

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