kae/musicmuster
1
0
Fork 0
Code Issues 28 Pull Requests Projects Releases 1 Activity

SQLAlchemy sessions poorly implemented #5

New Issue
Closed
opened 2021-06-01 08:51:05 +01:00 by kae · 0 comments
kae commented 2021-06-01 08:51:05 +01:00
Owner
Copy Link

Currently, one session is started when application starts, and is used forever. If MySQL goes away or the session times out, the app will fail.

The correct way of using sessions is to create a session for a group of related database tasks, and close it once those tasks are complete.

Currently, one session is started when application starts, and is used forever. If MySQL goes away or the session times out, the app will fail. The [correct way of using sessions](https://docs.sqlalchemy.org/en/14/orm/session_basics.html#when-do-i-construct-a-session-when-do-i-commit-it-and-when-do-i-close-it) is to create a session for a group of related database tasks, and close it once those tasks are complete.
kae closed this issue 2021-06-02 08:28:24 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
bug

Something is not working

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
help wanted

Need some help

  
invalid

Something is wrong

  
Priority

Work on soon

  
question

More information is needed

  
V5

   
wontfix

This won't be fixed

No Label
bug
duplicate
enhancement
help wanted
invalid
Priority
question
V5
wontfix
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: kae/musicmuster#5
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?