﻿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
15130	Model.validate_unique method doesn't take in account multi-db	Tetsuya Morimoto		"Model.validate_unique() method has 2 methods, _perform_unique_checks() and _perform_date_checks(), which use _default_manager for queryset. But, they are not considered with multi-db, that queryset is as follows.

{{{
qs = model_class._default_manager.filter(**lookup_kwargs)
}}}

I encountered a problem when ModelForm.is_valid() method is called since BaseModelForm calls full_clean() -> post_clean() -> validate_unique(). I could add/change/delete data with multi-db in AdminSite by setting arbitrary database with ""using"" keyword. However, the validation uniqueness check is invalid if default database has the same data.

# see also[[BR]]
http://docs.djangoproject.com/en/dev/topics/forms/modelforms/#the-is-valid-method-and-errors [[BR]]
http://docs.djangoproject.com/en/dev/ref/models/instances/#validating-objects

I only tested default table operation in AdminSite applying attached patch.[[BR]]
It works for me."	Bug	new	Database layer (models, ORM)	1.2	Normal		multi-db	botondus@… Carlos Palol Menno Manheim	Accepted	1	0	0	1	0	0
