byrman
commented
2 years ago I don't think this is a good idea:
while True:
await asyncio.sleep(10)
users = db_read_users(limit=100000)
for user in users:
print(f"tick: {tick}, user: {user} , reminders: {user.reminders}")
def db_read_users(
*,
only_active_users: bool = True,
session: Session = next(get_session()),
offset: int = 0,
limit: int = 100,
):
passYour default argument is evaluated only once, so each invocation is using the same session, which is never closed. If you do this instead, new reminders will be seen immediately:
while True:
await asyncio.sleep(10)
for session in get_session():
users = db_read_users(session=session, limit=100000)
for user in users:
print(f"tick: {tick}, user: {user} , reminders: {user.reminders}")This might be tempting, but won't properly close your connections (control flow is not resumed after get_session's yield):
while True:
await asyncio.sleep(10)
users = db_read_users(session=next(get_session()), limit=100000)
for user in users:
print(f"tick: {tick}, user: {user} , reminders: {user.reminders}")
omerXfaruq
First Check
Commit to Help
Example Code
Demo Repo
Description
I encountered an error while working on my side project Memory-Vault. After digging it inside and out I realized that error is due to the sqlmodel itself.
Flow:
Operating System
macOS
Operating System Details
No response
SQLModel Version
0.0.3
Python Version
Python 3.7.12
Additional Context
No response