---
title: "Integrazione di Django con database obsoleti"
version: 3.2
locale: it
source: https://docs.djangoproject.com/it/3.2/howto/legacy-databases/
canonical: https://djangodocs.dev/it/3.2/howto/legacy-databases/
---
# Integrazione di Django con database obsoleti

Mentre Django è adatto a sviluppare nuove applicazioni, e tuttavia possibile integrarlo con database obsoleti. Django include alcuni strumenti per automatizzare il più possibile il processo.

Questo documento presume che tu sappia le basi di Django, come ?descritto? nella sezione [tutorial](/it/3.2/intro/tutorial01/).

Once you’ve got Django set up, you’ll follow this general process to integrate
with an existing database.

## Dai a Django i tuoi parametri del database

You’ll need to tell Django what your database connection parameters are, and
what the name of the database is. Do that by editing the [`DATABASES`](/it/3.2/ref/settings/#std-setting-DATABASES)
setting and assigning values to the following keys for the `'default'`
connection:

- [`NAME`](/it/3.2/ref/settings/#std-setting-NAME)
- [`ENGINE`](/it/3.2/ref/settings/#std-setting-DATABASE-ENGINE)
- [`USER`](/it/3.2/ref/settings/#std-setting-USER)
- [`PASSWORD`](/it/3.2/ref/settings/#std-setting-PASSWORD)
- [`HOST`](/it/3.2/ref/settings/#std-setting-HOST)
- [`PORT`](/it/3.2/ref/settings/#std-setting-PORT)

## Generazione automatica dei modelli

Django comes with a utility called [`inspectdb`](/it/3.2/ref/django-admin/#django-admin-inspectdb) that can create models
by introspecting an existing database. You can view the output by running this
command:

```bash
$ python manage.py inspectdb
```

Save this as a file by using standard Unix output redirection:

```bash
$ python manage.py inspectdb > models.py
```

This feature is meant as a shortcut, not as definitive model generation. See the
[`documentation of inspectdb`](/it/3.2/ref/django-admin/#django-admin-inspectdb) for more information.

Once you’ve cleaned up your models, name the file `models.py` and put it in
the Python package that holds your app. Then add the app to your
[`INSTALLED_APPS`](/it/3.2/ref/settings/#std-setting-INSTALLED_APPS) setting.

By default, [`inspectdb`](/it/3.2/ref/django-admin/#django-admin-inspectdb) creates unmanaged models. That is,
`managed = False` in the model’s `Meta` class tells Django not to manage
each table’s creation, modification, and deletion:

```bash
class Person(models.Model):
    id = models.IntegerField(primary_key=True)
    first_name = models.CharField(max_length=70)
    class Meta:
       managed = False
       db_table = 'CENSUS_PERSONS'
```

If you do want to allow Django to manage the table’s lifecycle, you’ll need to
change the [`managed`](/it/3.2/ref/models/options/#django.db.models.Options.managed) option above to `True`
(or remove it because `True` is its default value).

## Install the core Django tables

Next, run the [`migrate`](/it/3.2/ref/django-admin/#django-admin-migrate) command to install any extra needed database
records such as admin permissions and content types:

```bash
$ python manage.py migrate
```

## Test ed aggiustamenti

Those are the basic steps – from here you’ll want to tweak the models Django
generated until they work the way you’d like. Try accessing your data via the
Django database API, and try editing objects via Django’s admin site, and edit
the models file accordingly.
