Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(sqlite): id column should be unique #894

Merged
merged 3 commits into from
May 12, 2024

Conversation

Monirzadeh
Copy link
Collaborator

This PR try to fix #892

Copy link

codecov bot commented Apr 27, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 30.77%. Comparing base (595cb45) to head (5fa2f1a).
Report is 24 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #894      +/-   ##
==========================================
+ Coverage   25.58%   30.77%   +5.19%     
==========================================
  Files          47       62      +15     
  Lines        5628     4461    -1167     
==========================================
- Hits         1440     1373      -67     
+ Misses       3989     2866    -1123     
- Partials      199      222      +23     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Member

@fmartingr fmartingr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Did you test the migration with data manually on your end?

@fmartingr fmartingr changed the title fix: ID should be uniq in sqlite database fix(sqlite): id column should be unique May 6, 2024
@Monirzadeh
Copy link
Collaborator Author

i test that in my side and i don't see any problem.

@Monirzadeh
Copy link
Collaborator Author

Monirzadeh commented May 12, 2024

today i thinking about a specific situation. should we handle id that currently reuse in database?

@fmartingr
Copy link
Member

today i thinking about a specific situation. should we handle id that currently reuse in database?

I don't think so. It already happened and we are avoiding it in the future now.

@fmartingr fmartingr merged commit 27283e9 into go-shiori:master May 12, 2024
12 checks passed
fmartingr added a commit that referenced this pull request May 12, 2024
Co-authored-by: Felipe Martin <812088+fmartingr@users.noreply.github.com>
@fmartingr fmartingr added this to the 1.7.0 milestone May 12, 2024
@Monirzadeh Monirzadeh deleted the fix-sqlite-uniq-id branch May 12, 2024 15:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

Shiori auto increasment not work currectly on sqlite database
2 participants