That indicates that you have data that was stored in the data cache before the software was upgraded, and the new version doesn’t know how to read it. This is a mistake we’ve made once or twice, but try to avoid. Did you recently upgrade? Furthermore, did you upgrade from a fairly old version? The change that broke this object happened over 9 months ago.
To fix it, you have two options, depending on how important the cached data is to you. First, you can just delete the data cache file (with Ignition stopped), and it will make a new one on startup. The data cache folder will be under the “datacache” folder, with the name of the db connection. The second option, if the data is important, is to simply rename the folder, and zip it up and send it to me. I can export the data and send it back to you. It’s not exactly an easy process, but I try to do what I can to save data.
Exception: Error executing expression binding on
Alarm Summary.Root Container.Alarms.AlarmTable.data
caused by ExpressionException: Error executing script for runScript() expression:app.alarms.get_history_alarms()
caused by Traceback (innermost last):
File "<expression:runScript>", line 1, in ?
File "<module:alarms>", line 10, in get_history_alarms
com.inductiveautomation.ignition.client.gateway_interface.GatewayException: ERROR: column "system" does not exist
Position: 8
Caused by: org.postgresql.util.PSQLException: ERROR: column "system" does not exist
Position: 8
Funny thing is this only shows up in the designer. The client never gets this error popup.
I’ve checked the alarm_log table and column ‘system’ does not exist. column ‘SYSTEM’ does exist however.
I had to lowercase every other column name except for ‘displaypath’ as well.
This has to be caused by postgres column quoting. If I recall… didn’t you have to remove the quote character from the translator because it was screwing something up with SQLTags (the name of the index or something)?
The problem with column quoting is you can use it or not- as long as everything does the same thing. It’s likely the table was created with them turned on, and now they’re not, or vice-versa.
Check the db translator and see if the column quote character is set. In this case, I believe the alarm log profile lets you define the column names, so you might be able to change the system column specification to be “SYSTEM”, with quotes.
Let me know what the settings currently are, though, and we can try to narrow it down. It’s possible that some part of the query is not getting properly quoted, one way or the other.
It would be under the database translator (Database>Drivers>Translator).
If it really was created when you had quoting turned on, and now you don’t, the only real solution would be to rename the columns. Actually, what I would probably do would be to rename the table, let Ignition create a new one, and then do a “insert into tablename select * from oldname”… except that your select might have to spell the columns out, to account for the differences.
I really hate case sensitivity and everything about that column quote setting…
[quote=“Colby.Clegg”]I really hate case sensitivity and everything about that column quote setting…
[/quote]
Try being the lone linux user in a MAC shop. MySQL sucks at this case stuff.
Did this change in 7.3.x?