Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#388 closed enhancement (wontfix)

Prefix for django table names

Reported by: Brendan O'Connor <brenocon@…> Owned by: adrian
Component: Metasystem Version:
Severity: normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:


It's mentioned at you can't change the names of the django tables in the database.

Proposal: use a prefix, like "_dj_", for all those tables. So you'd have in the database:



This would make browsing your schema easier, since your application-specific schemas wouldn't be interspersed with django-specific metasystem tables in an alphabetical listing. It would also make migrating from legacy databases easier, or interoperation with non-django systems, or indeed any operation that requires direct use of the DB.

Attachments (0)

Change History (2)

comment:1 Changed 9 years ago by adrian

  • Resolution set to wontfix
  • Status changed from new to closed

Yeah, we've considered this, but it's a bit too late at this point to rename those.

comment:2 Changed 9 years ago by Brendan O'Connor <brenocon@…>

Seems like it's a matter of going through the list of tablenames, and for each one running a massive find-and-replace, taking care not to bork those strings when they're appearing in places outside SQL... right?

I've done things like this before with grep and emacs, and there are IDE's that do it very nicely. I could give it a spin if someone who knows the code better could help out testing the patch.

Add Comment

Modify Ticket

Change Properties
<Author field>
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.