What databases can i use with django

Asked 9 years, 8 months ago. Active 1 month ago. Viewed 40k times. Improve this question. Ivan Vashchenko Ivan Vashchenko 1, 2 2 gold badges 10 10 silver badges 19 19 bronze badges. Add a comment. Active Oldest Votes. Give strong preference to more recent articles. Try to make sure you are comparing MySQL 5. MySQL let's you choose your storage engine. Keep in mind that you may not need all of the features of InnoDB or Postgres.

You should also look at some of the other Storage engines. Improve this answer. David S David S Note that mongoDB is non relational, so very different to the databases supported out of the box by Django. Mark Lavin Mark Lavin I didn't ask anyone to research them, I just thought that someone here would know about them and care to explain. Since this is primarily a learning experience, just use sqlite3 for now while you're learning Django.

Later, when working on a real project, you'll have to decide which db to use based on requirements. If all else is equal, just use mysql since you already know it. Long story short: for learning Django it doesn't matter. Add a comment. Active Oldest Votes. You can eliminate Oracle because it is proprietary. SQLite is quite different because the database is a file, there is no need for a running daemon.

Improve this answer. It really depends on the needs of your application and environment and also what you are comfortable with taking on. Enforces or not a transaction for each view request. By default set to False, because opening a transaction for every view has additional overhead.

The impact on performance depends on the query patterns of an application and on how well a database handles locking. By default set to True, because otherwise it would require explicit transactions to perform commits. The lifetime of a database connection in seconds. By default 0 which closes the database connection at the end of each request. Use None for unlimited persistent connections. PostgreSQL specific configuration to disable use of server-side cursors, used in scenarios with database pooling and pooling.

Defines a database host, where an empty string means localhost. If this value doesn't start with a forward slash, then this value is assumed to be the host. The name of the database to use. For SQLite, it's the full path to the database file. When specifying the path, always use forward slashes, even on Windows e. Extra parameters to use when connecting to the database. Available parameters vary depending on database brand, consult the Django database engine package's documentation.

See Table for a list of Django database engine packages. The port to use when connecting to the database. An empty string means the default port. To update records, you change the instance data and call the save method again. Each subsequent call to the save method will update the record:. To ensure records are updated in the most efficient manner possible, use the update method.

Rewriting the above process to use the update method, you get:. You can also use update to modify multiple records. The return value tells you that update has changed two records in the database. If you check the database, you will also see that all events at the bar have moved to the casino Figure 4. The return value for the delete method lists the total number of records affected one in this example , a dictionary listing the tables affected by the delete operation, and the number of records deleted in each table.

To prevent accidental deletion of all the data in a table, Django requires you to use the all method explicitly to delete everything in a table.

This is primarily due to well-established database design best-practice. If you were only saving the venue name in the database, you could get away with repeating the name of the venue multiple times in your database records. But what about if you wanted to save more information for the venue?

Your venue records should also include an address, telephone number, website address and email. If you add these fields to your events table, you can see that you will end up with a lot of repeated information, not to mention the nightmare of ensuring you update all records if some venue information changes. Database normalization is the process of designing your tables to minimize or eliminate data repetition.

In simple terms, normalization is keeping related data in separate tables and linking tables via relationships hence the name relational database.

So, as you would expect, Django makes creating relationships between tables of related information simple. With our venue example, it would be good practice to have all the venue information in one table, and link to that information from the event table.

We create this link in Django with a foreign key. Multiple events linking to one venue record is an example of a many-to-one relationship in relational database parlance. Looking at the relationship in the opposite direction, we get a one-to-many relationship , i.

Django provides QuerySet methods for navigating relationships in both directions—from one to many, and from many to one—as you will see shortly. There is one other common database relationship that we need to explore, and that is the many-to-many relationship. An excellent example of a many-to-many relationship is the list of people who are going to an event.

Each event can have many attendees, and each attendee can go to multiple events. Note the order of the classes. Remember, this is Python, so the order of the models in your models. The new model classes need to be declared before the Event model for the Event model to be able to reference them. The Venue model is very similar to the Event model, so you should find it easy to understand.