Feature/infered user tables #65
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces a new inferred user tracking system to the database schema and ORM models. The main changes add three new tables—
inferred_user
,session
, andendpoint_request
—to theuser_related
schema, along with corresponding SQLAlchemy models to support user session tracking and endpoint request logging.Database schema additions:
alembic/versions/e354666f951d_inferred_user.py
to create theinferred_user
,session
, andendpoint_request
tables in theuser_related
schema. Each table includes relevant columns, primary keys, and foreign key relationships for session and request tracking.ORM model additions:
InferredUser
,Session
, andEndpointRequest
SQLAlchemy models inwelearn_datastack/data/db_models.py
, mirroring the new tables and relationships defined in the migration. These models allow application code to interact with inferred users, sessions, and endpoint requests.