Database Management » History » Version 1
digitalcircuit, 06/17/2018 08:09 PM
| 1 | 1 | digitalcircuit | h1. Database Management |
|---|---|---|---|
| 2 | 1 | digitalcircuit | |
| 3 | 1 | digitalcircuit | Most tasks involving the can be accomplished within Quassel itself, and when possible, you should use those options (_e.g. deleting chat by right-clicking buffers, Delete Chats_). However, some actions, such as deleting Quassel users, deleting backlog older than a certain date, and cleanup require manually modifying the database while the Quassel core is stopped. |
| 4 | 1 | digitalcircuit | |
| 5 | 1 | digitalcircuit | The steps to take depend on which database backend you're using. If you don't know, it's most likely *SQLite*. |
| 6 | 1 | digitalcircuit | |
| 7 | 1 | digitalcircuit | See the pages for... |
| 8 | 1 | digitalcircuit | |
| 9 | 1 | digitalcircuit | * [[SQLite]] |
| 10 | 1 | digitalcircuit | * [[PostgreSQL]] |
| 11 | 1 | digitalcircuit | |
| 12 | 1 | digitalcircuit | h2. Migrating SQLite to PostgreSQL |
| 13 | 1 | digitalcircuit | |
| 14 | 1 | digitalcircuit | In many cases, PostgreSQL offers better performance and greater reliability than SQLite. |
| 15 | 1 | digitalcircuit | |
| 16 | 1 | digitalcircuit | To migrate, see the setup and migration documentation on [[PostgreSQL]]. |