Diederik van der Boor 8cf313335c Handle stale ContentType models (no longer referring to a model) ...

This builds on top of a fix in Django 1.6, and has a workaround for
Django 1.4 and 1.5. When the base class points to a model that no longer
exists, it will be silently dropped in the polymorphic queryset results.

This behavior is identical to iterating over results when the derived
table doesn't have the object anymore.

2013-05-19 14:35:29 +02:00

..

templates/admin/polymorphic

Remove unused load statements in add_type_form.html

2013-03-18 12:15:10 +01:00

templatetags

Added polymorphic admin interface

2012-07-05 23:16:46 +02:00

__init__.py

Version 0.4.2 proper

2013-04-10 14:18:55 +02:00

__version__.py

Bumped versio to .dev0

2013-04-10 14:23:29 +02:00

admin.py

Apply list filter in example app

2013-04-08 00:37:51 +02:00

base.py

Fix base_manager unit test

2013-04-08 00:32:02 +02:00

compatibility_tools.py

PEP 8 cleaning

2011-12-20 18:59:50 +00:00

manager.py

Fix passing custom querysets to related managers.

2013-04-07 01:39:58 +02:00

models.py

IMPORTANT: import path changed, it's now: "from polymorphic import PolymorphicModel, ..."

2010-02-22 16:16:00 +01:00

polymorphic_model.py

Handle stale ContentType models (no longer referring to a model)

2013-05-19 14:35:29 +02:00

query_translate.py

Support proxy models (still requires one query per proxied model, not optimal)

2013-04-07 23:36:09 +02:00

query.py

Handle stale ContentType models (no longer referring to a model)

2013-05-19 14:35:29 +02:00

showfields.py

PEP 8 cleaning

2011-12-20 18:59:50 +00:00

tests.py

Updated proxy model tests

2013-04-08 00:32:06 +02:00

tools_for_tests.py

Update db_type method for Django >= 1.4 DB settings format.

2013-03-18 20:50:45 +01:00