== Proposed features for Django 1.1 == Please list any proposed features for 1.1 below, along with links to relevent tickets, django-dev discussions, etc. * [http://code.google.com/p/django-aggregation/ ORM aggregation] (see also [http://groups.google.com/group/django-developers/browse_thread/thread/749ebaf0fa80f807/892c890bc5f1f551 this django-dev thread]) * [ticket:6845 model validation] * [http://groups.google.com/group/django-developers/browse_thread/thread/5482009f35c9cff5 Manager.update_or_create] (see also #3182) * [http://groups.google.com/group/django-developers/browse_thread/thread/09f0353fe0682b73 multiple database APIs] * [http://groups.google.com/group/django-developers/browse_thread/thread/f04aed2bc60274f0 better HTML output for form fields] (see also [http://code.google.com/p/django-html/ django-html]) * [http://groups.google.com/group/django-developers/browse_thread/thread/9f5d117fdbb05a12 customizability of contrib.comments] (see also #8630) * [ticket:7338 Cache queryset results] * [ticket:6735 Class-Based Generic Views] * [ticket:7210 Referencing fields in queries and updates in the ORM] (possibly part of django aggregation, I know the GSOC student has worked on this) * [ticket:9093 Extend inclusion tag syntax to allow custom templates] * [http://groups.google.com/group/django-developers/browse_thread/thread/3417b90f0e6fda9f URL resolver refactor] * [http://www.youtube.com/watch?v=M1Qr9rSBGBE&feature=PlayList&p=D415FAF806EC47A1&index=2 Multiple edit arbitrary fields in the admin]