Skip to content

Commit fefad9f

Browse files
authored
Make FAQ questions bold
1 parent 8991456 commit fefad9f

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -95,19 +95,19 @@ Installation
9595
FAQ - Frequently asked questions
9696
--------------------------------
9797

98-
1. Why do I need to change the database back-end/engine?
98+
1. **Why do I need to change the database back-end/engine?**
9999

100100
We utilize PostgreSQL's `hstore` data type, which allows you to store key-value pairs in a column. In order to create `UNIQUE` constraints on specific key, we need to create a special type of index. We could do this without a custom database back-end, but it would require everyone to manually write their migrations. By using a custom database back-end, we added support for this. When changing the `uniqueness` constraint on a `HStoreField`, our custom database back-end takes care of creating, updating and deleting these constraints/indexes in the database.
101101

102-
2. I am already using a custom database back-end, can I still use yours?
102+
2. **I am already using a custom database back-end, can I still use yours?**
103103

104104
Yes. You can set the ``POSTGRES_EXTRA_DB_BACKEND_BASE`` setting to your current back-end. This will instruct our custom database back-end to inherit from the database back-end you specified. **Warning**: this will only work if the base you specified indirectly inherits from the standard PostgreSQL database back-end.
105105

106-
3. Does this package work with Python 2?
106+
3. **Does this package work with Python 2?**
107107

108108
No. Only Python 3.5 or newer is supported. We're using type hints. These do not work well under older versions of Python.
109109

110-
4. Does this package work with Django 1.X?
110+
4. **Does this package work with Django 1.X?**
111111

112112
No. Only Django 1.10 or newer is supported.
113113

0 commit comments

Comments
 (0)