Enhance Database Modeling and SQLAlchemy Compatibility #1593
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 makes several changes to the
backend/app/models.py
file to enhance database modeling and improve compatibility with SQLAlchemy. The key updates include adjustments to field definitions, changes to relationships, and the removal of certain constraints.Changes to field definitions:
email
field inUserBase
to explicitly usesa_type=String(255)
for better SQLAlchemy compatibility.email
field type inUserRegister
,UserUpdate
, andUserUpdateMe
fromEmailStr
tostr
for consistency and to avoid type-related issues.Changes to relationships:
items
relationship in theUser
model to includesa_relationship_kwargs
for defining cascading behavior and specifying join conditions.owner_id
field in theItem
model to remove theforeign_key
constraint while keeping it indexed for performance. Addedsa_relationship_kwargs
to theowner
relationship for explicit join conditions.