Possible minor contradiction in DATABASES setting depicted in multiple database/routing docs example.

[aleks]

Whilst perusing the (excellent) documentation, I noticed that in the 'Multiple databases' docs (​https://docs.djangoproject.com/en/1.8/topics/db/multi-db/), the section 'Defining your databases' states: "Django requires that a default database entry be defined, but the parameters dictionary can be left blank if it will not be used"...

However in the example later in this section (​https://docs.djangoproject.com/en/1.8/topics/db/multi-db/#an-example), the default value is not defined.

I fully appreciate this is an example, which as stated skips some complex considerations, however from what I understood, the default value is a *requirement* not a consideration as such?

Or have I misunderstood/misread the requirement for the 'default' value when using custom routers? (in which case my apologies!)

[Tim Graham]

I believe the correct solution is to add 'default': {} to those examples, but we should double check.

[Tim Graham]

​PR

[Iacopo Spalletti]

Setting DATABASES as stated in current documentation returns an error.
Linked PR fixes the issue

[Tim Graham <timograham@…>]

In ac750db:

Fixed #25681 -- Added 'default' to DATABASES example.

[Tim Graham <timograham@…>]

In a98d08f9:

[1.9.x] Fixed #25681 -- Added 'default' to DATABASES example.

Backport of ac750dbbc0533dcf9c2f6c0f09957adf6f976d3e from master

[Tim Graham <timograham@…>]

In 189ceae1:

[1.8.x] Fixed #25681 -- Added 'default' to DATABASES example.

Backport of ac750dbbc0533dcf9c2f6c0f09957adf6f976d3e from master