Patriot Database Schema
Restrictions
In some cases, it may be useful to access the Patriot database directly. Patriot has an open database, which means that direct access is allowed as long as the following restrictions are followed.
Reading Data
For access to custom data access, the recommended approach is to use a GraphQL report, which has more up to date documentation. Alternatively, it's possible to read data directly from the Patriot database. The only concern you should have is the additional workload of running queries on the server. Poorly written queries can have a dramatic impact on server performance.
Inserting / Updating / Deleting Data
Changing data in the Patriot database is not recommended. While the database does have some integrity built in, we cannot protect against all possible invalid data being inserted into the database. Serious caution must be taken before any data is changed in the database. Patriot takes no responsibility from the consequences of invalid data inserted or changed outside of Patriot itself. A much safer way to alter the data in the database is by using the JSON Services or Patriot SDK features.
Altering the database structure
Under no circumstances should the database structure be altered in any way. Altering the database structure includes adding/modifying tables, table columns, keys, constraints etc.
Schema File
A Microsoft Excel spreadsheet containing details about the Patriot database structure can be downloaded here:
You will need a copy of Microsoft Excel to view the spreadsheet, or alternatively you can use the Microsoft Excel Viewer for readonly access to the file.