Alarm Journal + PostgreSQL Schemas

The alarm journal allows one to specify the table name to store events and event data. However, if the table is in a non public schema, such as then the gateway complains about the table name having a period.

Is there any chance of this being fixed?



2 years later… And I stumbled across the same issue, but using SQL Server.
I have two alarm journals, each one intended to be on a different schema but on the same DB.

Is it going to be fixed?

Almost two years later… this is still an issue in Ignition v8.1.17… and PostgreSQL v12 or v13…