...
Note | ||
---|---|---|
| ||
Note: as of Bedework 3.7, PostgreSQL is the preferred database system used by Bedework. |
...
Name them something like: bedework3p10 bedework_cal, bedework3p10bedework_synch, bedework3p10bedework_card, bedework3p10bedework_reg.
Provide full access rights to an appropriately named user such as bedework.
...
Info | ||
---|---|---|
| ||
# \list Name | Owner | Encoding | Collation | Ctype | Access privileges ------------------+----------+----------+-------------+-------------+----------------------- bedework3p10 bedework_cal | bedework | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =Tc/bedework : bedework=CTc/bedework bedework3p10 bedework_card | bedework | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =Tc/bedework : bedework=CTc/bedework bedework3p10 bedework_reg | bedework | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =Tc/bedework : bedework=CTc/bedework bedework3p10 bedework_synch | bedework | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =Tc/bedework : bedework=CTc/bedework |
...
- MS SQL Server: Partially supported but requires at least hand-editing of the schema. Has not been tried with 3.3.1 onwards. At least one problem remains, Sql Server does not follow the ANSI standard for unique indexes in that null=null for Sql Server but null is never equal to null in ANSI standard databases. This breaks some of the unique indexes in Bedework.MySQL version 4: Has problems in a number of areas. These are unlikely to ever be resolved. Version 4 is now old.
Developer notes
There are no checks that the application, e.g the calendar, has the same settings as the database. Databases will interpret the byte stream according to their configuration even if that does not match the configuration of the calendar server. Care in matching up all the components is critical. Those components are at least:
...