Opened 15 years ago

Closed 13 years ago

#11391 closed Bug (duplicate)

Legacy Database "%" escaping not documented

Reported by: Greg Owned by: nobody
Component: Core (Management commands) Version: 1.0
Severity: Normal Keywords: legacy, models.py inspectdb
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

While creating a model for a legacy database using inspectdb, I was not able to retrieve data from a column where db_column referenced a field with a % i.e. Discount%. Eventually, through the help here http://groups.google.com/group/django-users/browse_thread/thread/162a4e857d15248c I learned that it is necessary to escape the % with a %%, which makes sense overall, but was not obvious in the context of the model design.

The need to escape the % with %% is not documented as far as I can tell and should either be automatic with inspectdb or included in the Integrating Django with a legacy database documentation (I leaning towards the latter). Other such non-obvious (at least for relatively new python and django users) aspects of dealing with a legacy database should also be documented more clearly, perhaps in a Things To Look Out For section for example.

Thank you.

Change History (8)

comment:1 by Greg, 15 years ago

Keywords: lecacy models.py added

comment:2 by Greg, 15 years ago

Keywords: legacy added; lecacy removed

comment:3 by Russell Keith-Magee, 15 years ago

Triage Stage: UnreviewedAccepted

comment:4 by Gabriel Hurley, 14 years ago

Component: django-admin.py inspectdbCore (Management commands)

comment:5 by Julien Phalip, 14 years ago

Severity: Normal
Type: Bug

See #6343 for a potentially related issue.

comment:6 by Julien Phalip, 14 years ago

See some other issues relating to the use of the % character and escaping: #3485, #6343, #12268, #13648. Perhaps some of these could be tackled at the same time.

comment:7 by Ramiro Morales, 13 years ago

Easy pickings: unset
Keywords: inspectdb added
UI/UX: unset

comment:8 by Alex Gaynor, 13 years ago

Resolution: duplicate
Status: newclosed

Marking as a duplicate of #6343.

Note: See TracTickets for help on using tickets.
Back to Top