Jump to content
On 9/26/2016 at 1:33 PM, Erik Sieghart said:

There are going to be three components here:

1) Your backend data layer. This will be driven by sql alchemy or something.

2) An internal controller which helps present and receive input from the user.
3) Your actual UI.

I know this is MVC, but the reason is because you're working with a database, and working with databases means you have to add a bunch of protections to ensure that the database cannot be corrupted or compromised. The user should never be talking directly through the database, should never be allowed to create their own queries, or otherwise inject code into the database under an circumstances. Use widgets to modify data and add checks into the middle controller to ensure the data is valid (effectively checking twice) before you send it to the database.

But I mean, I guess for something basic it's not all that necessary. I work with databases in the way you describe a lot (in Python no less), so I've just gotten in the habit of approaching it this way.

thank you for the reply, i will look into the sqlalchemy, i'm finding this quite difficult but i am sure i'll get there in the end

Link to comment
https://linustechtips.com/topic/666930-database-and-tkinter/#findComment-8615883
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×