This is an automated email from the ASF dual-hosted git repository. snoopdave pushed a commit to branch allow-same-origin-fonts-in-theme-csp in repository https://gitbox.apache.org/repos/asf/roller.git
commit eec233b11b0644501392405413083612440d0931 Author: David M. Johnson <[email protected]> AuthorDate: Tue Sep 8 07:05:26 2026 -0400 Document H2 2.5.250 VALUE reserved-word workaround H2 2.5.250 reserves VALUE, which several Roller tables use as a column name, so Roller fails to read them on that database. H2 is not an officially supported database, so document the ;NON_KEYWORDS=VALUE JDBC URL workaround in the install guide rather than changing the schema. Claude-Session: https://claude.ai/code/session_015X69HHQ5XnjRkJP8ymzwFf --- docs/roller-install-guide.adoc | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs/roller-install-guide.adoc b/docs/roller-install-guide.adoc index 89e620e19..651296047 100644 --- a/docs/roller-install-guide.adoc +++ b/docs/roller-install-guide.adoc @@ -259,6 +259,19 @@ be packaged as ojdbc14.jar, even if operating on Oracle 9 server. * See the server specific sections to information on where to place the JDBC driver jars. +=== H2 database considerations + +H2 is not one of Roller's officially supported databases (PostgreSQL, MySQL and +Derby are), but Roller can run against it as a generic JDBC database. If you use +H2 2.5.250 or later, be aware that H2 now treats VALUE as a reserved word. +Several Roller tables, such as ROLLER_PROPERTIES, have a column named VALUE, so +Roller will fail to read them on newer H2. To work around this, append +;NON_KEYWORDS=VALUE to your H2 JDBC connection URL, for example: + +---- +jdbc:h2:file:/path/to/rollerdb;NON_KEYWORDS=VALUE +---- + == Deploy Roller to Tomcat Deploying Roller to the Tomcat servlet container involves creating a
