id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
10509	Better handling of database version-specific feature initialisation	Malcolm Tredinnick	Christophe Pettus	"Right now, we have problems such as those mentioned in #10467 (comment 4). If a part of Django wants to use a particular feature that depends on the database version, it needs to first have talked to the database. This breaks in some edge-cases.

Some alternative possibilities are

 1. understanding deferred-features, but that looks hard. For example, it's difficult to imagine how ""return ID from insert"" can work in that fashion without being really ugly code.
 2. requiring the settings file to include the version information so we don't have to make the wasteful `SELECT version();` (or equivalent) call for every database connection. It's essentially unchanging information.

Anyway, that's a discussion for later (I'll start a thread on django-dev at some point). Opening the ticket to remind me to look at this."	Bug	closed	Database layer (models, ORM)	dev	Normal	wontfix		richard.davies@…	Accepted	0	0	0	0	0	0