@atlass218 I know I am weighing in on this a bit late but you do not want to reference you database backend from your Gui frontend (lookup MVC methodology). Further when building your database interface in pure python it is best to build it as a self-contained autonomous class that handles everything more generically and then all your frontend does is call preconfigured Methods passing in any parameters in as a dictionary that the database might need to use in the query. If you would like to see a templated version of this I have one that I share with my students that I can share with you as well
As far as dates go if they are stored as a DateTime object then they are without formatting and are stored as the number of seconds from a base date when you ask it to format that and give it a format it converts it. So unless you need to display the data you should never format it just leave it in its native state. And never work with the formatted version unless you are getting one from the User in which case its best to force the formatting you want or break the fields up in 3 separate entities and then behind the scenes do the conversion you self into a native DateTime object. I hope that helps you.
As far as dates go if they are stored as a DateTime object then they are without formatting and are stored as the number of seconds from a base date when you ask it to format that and give it a format it converts it. So unless you need to display the data you should never format it just leave it in its native state. And never work with the formatted version unless you are getting one from the User in which case its best to force the formatting you want or break the fields up in 3 separate entities and then behind the scenes do the conversion you self into a native DateTime object. I hope that helps you.