#36039 closed New feature (wontfix)
Add command for Fetching all table names and columns
| Reported by: | Arian Omrani | Owned by: | Hana Belay |
|---|---|---|---|
| Component: | Core (Management commands) | Version: | 5.1 |
| Severity: | Normal | Keywords: | manage.py, command |
| Cc: | Arian Omrani | Triage Stage: | Unreviewed |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | yes | UI/UX: | no |
Description
Fetch, Prints and saves all table names and columns from all apps.
Attachments (1)
Change History (5)
by , 11 hours ago
| Attachment: | export_table_info.py added |
|---|
comment:1 by , 10 hours ago
| Owner: | set to |
|---|---|
| Status: | new → assigned |
comment:2 by , 9 hours ago
comment:3 by , 9 hours ago
| Resolution: | → wontfix |
|---|---|
| Status: | assigned → closed |
Thanks for the suggestion. Generally, feature requests should be made on the Django forum to get a consensus about whether or not to include them. I'm afraid this command is likely too niche to be included. It's not clear why this command would be a common need for developers.
comment:4 by , 9 hours ago
Ok, thanks. I just realized that I didn't pay attention to the triage stage. I thought it was an accepted ticket that needed to be worked on.
Note:
See TracTickets
for help on using tickets.
Hi, I hope you are well. This is my first time trying to contribute to Django. I was checking this ticket and found the attached source code for the feature. Do we want to follow that strictly? I was wondering why it is using raw SQL queries instead of Django's ORM to fetch model metadata (?) Also, why not use a JSON file to store the output instead of plain text? I would love to hear your feedback. Thank you!