Re: [Django] #891: customize table name prefixes
Django
-------------------------------------+-------------------------------------
Reporter: aaronsw | Owner: adrian
Type: defect | Status: closed
Component: Database layer | Version:
(models, ORM) | Resolution: invalid
Severity: normal | Triage Stage: Ready for
Keywords: | checkin
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by anonymous):
* ui_ux: => 0
* easy: => 0
Comment:
I support this feature request.
--
Ticket URL: <https://code.djangoproject.com/ticket/891#comment:11>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
-------------------------------------+-------------------------------------
Reporter: aaronsw | Owner: adrian
Type: defect | Status: closed
Component: Database layer | Version:
(models, ORM) |
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by mcd-php):
I positively vote for this !
I created my project in ignorance of table naming convention, named it
like '''verbose_marketing_name_tld'''.
I generate my tables (and probably will generate my code) from XML, I have
'''lots''' of tables split into ''nested'' groups, and so sadly Django
does not support PostgreSQL schemas (I use schemas in data collection and
transformation staging database, otherwise i'd be lost in their numbers
and scroll off my mouse wheel). To make things more sad, my tables have
prefixes already.
So finally I end up with tables named like
'''verbose_marketing_name_tld_etla_somelongnoun_to_otherlongnoun''', and
it would be really handy to bend them into at least
'''vmnt_etla_somelongnoun_to_otherlongnoun''' by the single change, so
Don't Repeat Yourself.
Of course, it will take time to implement in framework and I must do my
task today, so I'll be forced to implement kludges and crutches, but this
feels so sad ...
--
Ticket URL: <https://code.djangoproject.com/ticket/891#comment:12>
Django
-------------------------------------+-------------------------------------
| Holovaty
Type: defect | Status: new
Component: Database layer | Version:
(models, ORM) |
Severity: normal | Resolution:
| checkin
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
* status: closed => new
* needs_better_patch: 0 => 1
* needs_tests: 0 => 1
* needs_docs: 0 => 1
* resolution: invalid =>
Old description:
> Currently if a table is defined in a module named gork.py then the tables
> will be prefixed with "gork_". There should be some way to override this.
New description:
Currently if a table is defined in a module named gork.py then the tables
will be prefixed with "gork_". There should be some way to override this.
I positively vote for this as well
--
--
Ticket URL: <https://code.djangoproject.com/ticket/891#comment:13>
Django
-------------------------------------+-------------------------------------
Reporter: aaronsw | Owner: Adrian
| Holovaty
Type: defect | Status: new
Component: Database layer | Version:
(models, ORM) |
Severity: normal | Resolution:
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 0 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Benjamin Math):
I think that this ticket feature should be added. My team needs to be able
to edit the prefixes as well. One line of settings config is much better
than controlling metadata on multiple tables individually.
--
Ticket URL: <https://code.djangoproject.com/ticket/891#comment:14>
Django
-------------------------------------+-------------------------------------
Reporter: aaronsw | Owner: Adrian
| Holovaty
Component: Database layer | Version:
(models, ORM) |
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
-------------------------------------+-------------------------------------
* status: new => closed
* severity: normal => Normal
* needs_better_patch: 1 => 0
* needs_tests: 1 => 0
* type: defect => New feature
* needs_docs: 1 => 0
* resolution: => wontfix
* stage: Ready for checkin => Unreviewed
Comment:
As described in comment 10, it's inappropriate to reopen this ticket
without a consensus on the DevelopersMailingList. Closing per
TicketClosingReasons/DontReopenTickets.
--
Ticket URL: <https://code.djangoproject.com/ticket/891#comment:15>