equal
deleted
inserted
replaced
39 Each instance can be configured with its own database connection information, |
39 Each instance can be configured with its own database connection information, |
40 that will be stored in the instance's :file:`sources` file. The database to use |
40 that will be stored in the instance's :file:`sources` file. The database to use |
41 will be chosen when creating the instance. CubicWeb is known to run with |
41 will be chosen when creating the instance. CubicWeb is known to run with |
42 Postgresql (recommended), SQLServer and SQLite. |
42 Postgresql (recommended), SQLServer and SQLite. |
43 |
43 |
44 Other possible sources of data include CubicWeb, Subversion, LDAP and Mercurial, |
44 Other possible sources of data include CubicWeb, LDAP and Mercurial, |
45 but at least one relational database is required for CubicWeb to work. You do |
45 but at least one relational database is required for CubicWeb to work. You do |
46 not need to install a backend that you do not intend to use for one of your |
46 not need to install a backend that you do not intend to use for one of your |
47 instances. SQLite is not fit for production use, but it works well for testing |
47 instances. SQLite is not fit for production use, but it works well for testing |
48 and ships with Python, which saves installation time when you want to get |
48 and ships with Python, which saves installation time when you want to get |
49 started quickly. |
49 started quickly. |