Opened 12 years ago
Closed 12 years ago
#19292 closed Bug (invalid)
syncdb ignores umask when creating a sqlite database
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | Core (Management commands) | Version: | 1.4 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
My settings.py is using the django.db.backends.sqlite3
backend, and the user running manage.py has umask value 0002. However, when running manage.py syncdb
for the first time, the sqlite database file is created with access rights 0644, ignoring the user's umask value.
Change History (2)
comment:1 by , 12 years ago
Component: | Database layer (models, ORM) → Core (Management commands) |
---|---|
Triage Stage: | Unreviewed → Accepted |
comment:2 by , 12 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
A quick search brings up this thread: http://www.mail-archive.com/sqlite-users@sqlite.org/msg59080.html
Apparently it's a bug in SQLite.
The same bug was reported against PHP and rejected for the same reason: https://bugs.php.net/bug.php?id=31573
It also exists in Python itself: