[I57] MySQL implementation #65

2023-02-12T12:56:56Z

rho_n commented

2023-02-12 12:56:56 +00:00

Add MySQL database support to the hpr templates. Unfortunately there are enough differences in the MySQL and SQLite query syntax (in particular when using date functions) that either separate branches in the repository would need to be maintained for each database or the templates would need to programatically adjust based on the current database being used.

I chose the later option. Now any SQL query that needs modified depending on the database being used is split out into a separate template with the following naming convention:
queries-<page name>-<database name>.tpl.html

These queries can be in the calling template with the following PROCESS MACRO:

With this, any supported database can be add by just including new query templates.

Add MySQL database support to the hpr templates. Unfortunately there are enough differences in the MySQL and SQLite query syntax (in particular when using date functions) that either separate branches in the repository would need to be maintained for each database or the templates would need to programatically adjust based on the current database being used. I chose the later option. Now any SQL query that needs modified depending on the database being used is split out into a separate template with the following naming convention: queries-\<page name\>-\<database name\>.tpl.html These queries can be in the calling template with the following PROCESS MACRO: \<!--% PROCESS "queries-\<page name name\>-${constants.database}.tpl.html" %--\> With this, any supported database can be add by just including new query templates.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: HPR/hpr_generator#65