Version 12 (modified by Gary Wilson <gary.wilson@…>, 18 years ago) ( diff )

Character encoding issues

Feature Grouping

This page was created as a way to collect tickets, wiki pages, etc. that have similar goals. A ticket keyword just isn't enough sometimes. Add a group, description, analysis, and/or links about a feature you are interested in. If there is too much information about the feature to fit on this page, then create a wiki page dedicated to that feature and link to it here.

Please note that there is already a grouping of VersionOneFeatures.

Character encoding issues

Several tickets are mentioned in this mailing list thread: ​unicode issues in multiple tickets (#952, #1356, #3370) and thread about Euro sign in django-users

Tickets:

Comments made by Michael in the above mailing list thread

The problem that started the original thread in django-users was that the MySQLdb backend thought it was using latin-1 encoding for the connection and therefore could not encode '€', which is in iso-8859-15 but not in iso-8859-1 aka iso-latin-1. Ticket #2896 seems to explain how this can happen.

In my opinion, each of the three tickets in the subject should solve this issue, and none tries to cope with templates written in a different encoding than settings.DEFAULT_ENCODING.

#952 allows to use a different encoding on the connection than settings.DEFAULT_CHARSET. It does it for all backends.

#1365 sets connection.charset in the mysql backend to utf8. This makes the MySQLdb use utf8 encoding, but it's hackish and has been reported not to work in all environments.

#3370 opens the mysql backend connection with charset='utf8', which seems a cleaner way to do the same as #1365. It also fixes the repr of models (not sure if this is the best way, but this can be added to any of the other patches)

My bottom line is that #952 has a different scope than the other two tickets, and that #1365 should be closed as duplicate of #3370. #3370 and #952 can co-exist.

Pagination

There are a few tickets aiming to add features to the Paginator class, and even a new implementation by Adrian in #1374. There is also code for a PaginatorTag.

#1795, #1374, #3169, #3170, #2603

Multiple edit_inline issues

  • weird interaction with auto_now_add on update raising an exception (#2717)
  • Multiple FileFields & edit_inline interaction overwriting preceeding files (#2413, #792)
  • interacting with a specific unique_together ordering (#2470, #526, #2415)
  • problems with unique (#565)
  • edit_inline deleting stuff (#3425)
  • validator issues: (#265, #1690, #3043)
  • Manipulator allowing "stealing" of related objects (#3145)
  • Multiple Foreign Keys (#1939 & another 3 or 4 tickets marked as dupes)
  • Not using a sensible default state (#2159)
  • Causing KeyError, when follow=False in manipulator constructor or editable=False in model definintion (#2434, #1603)
  • Causing IndexError (#3519)
  • OneToOne fields (#24)
  • Ignoring things with core=True (#2724)
  • Non-working prepopulate from (#957)
  • A possible better way of doing things (which Adrian says is "fantastic") #2248 (*note: backwards incompatible change)
  • Problem with auto_now_add (#1030)
  • Admin ordering not working (#2679)
  • feature: Javascript adding/deleting in admin interface (#13)
  • collapsing in admin interface (#494)

Incorrect SQL construction

There are a bunch of these, so here's a placeholder for them. Many are already assigned to mtredinnick; the remainder should be. I'm working on a rewrite of the query creation portion of QuerySets -- Malcolm.

Web services

Tickets:

  • Models CRUD via web services (#115) with a lot of duplicates
  • [patch] XMLRPC support for django (#547) for part of a solution (set as duplicate of #115)

On the web:

On mailing-lists:

Note: See TracWiki for help on using the wiki.
Back to Top