Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#26757 closed Uncategorized (invalid)

sqlsequencereset Doesn't do auth_* django_* tables

Reported by: Vackar Afzal Owned by: nobody
Component: contrib.auth Version: 1.9
Severity: Normal Keywords: Sequences, Oracle, IDs
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: yes UI/UX: no


I've ran sqlsequencereset and noticed it doesn't print the SQL for tables starting in auth_* or django_*

Is this expected behaviour, or is there a bug somewhere that isn't bringing these models forward?

Change History (4)

comment:1 Changed 7 years ago by Baptiste Mispelon


The documentation for sqlsequencereset [1] indicates that you have to give it at least one app name (like auth or contenttypes, ...).

When I try python sqlsequencereset auth on my local version, I get the expected output (using postgresql).

Could you show us the exact command you're running and its output? Also, which database are you using?



comment:2 Changed 7 years ago by Vackar Afzal

Apologies, just check with the devs and you are right, forgot to include 'auth' as one of the apps.
Please feel free to close this off now.

comment:3 Changed 7 years ago by Baptiste Mispelon

Resolution: invalid
Status: newclosed

Thanks for checking.

I've closed the bug but for reference, you don't need any special permissions to close a ticket here.

comment:4 Changed 7 years ago by Vackar Afzal

Thanks :-)

Note: See TracTickets for help on using tickets.
Back to Top