#29874 closed Cleanup/optimization (fixed)
Use .tables for SQLite in tutorial 02
| Reported by: | wonhyeongseo | Owned by: | Vishvajit Pathak |
|---|---|---|---|
| Component: | Documentation | Version: | 2.1 |
| Severity: | Normal | Keywords: | typo |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | yes | UI/UX: | no |
Description
There is a typo in the last sentence of the paragraph after the first code block with the command;
python manage.py migrate
To show the table names in SQLite, .tables is used rather than .schema.
Change History (4)
comment:1 by , 6 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 6 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | assigned → closed |
I think either .schema or .tables is fine. (.schema gives the full SQL vs just the table name.)
Admittedly the .table command is probably closer in output to the other examples for the other DBs but I don't think the change is worth triggering re-translations. As such, I'll opt for wontfix.
comment:3 by , 3 years ago
| Cc: | removed |
|---|---|
| Resolution: | wontfix → fixed |
| Summary: | Typo in "Writing your first Django app, part2". → Use .tables for SQLite in tutorial 02 |
In 9466fd78420a851460c92673dad50a5737c75b12:
Recommended using .tables on SQLite in tutorial 2.
(#30606 is a duplicate and merged PR 14909 proposed this again).
Note:
See TracTickets
for help on using tickets.
I feel it's fine if we even show the schema here.