Hello,
I’m experiencing a persistent issue in CMDBuild 4.0 related to a deleted attribute that continues to cause SQL errors.
Context:
- I created a class named SEE_Scope with an attribute called ScopeType.
- Later, I deleted the ScopeType attribute and created a new one in its place.
- Despite this, when I try to access the class records in the application, I get an SQL error indicating that the system is still trying to query the deleted ScopeType attribute.
Error:
* *org.cmdbuild.dao.DaoException: error executing query = * *'SELECT ... "ScopeType" _scopetype FROM "SEE_Scope" ...', * *caused by: org.postgresql.util.PSQLException: ERROR: column "ScopeType" does not exist* *
What I’ve tried:
- Deleted and recreated the class SEE_Scope.
- Verified that the ScopeType column no longer exists in the database.
- Removed all filters, views, default sorting, and import/export templates referencing ScopeType.
- Reloaded metadata and restarted the server.
- Even recreated the ScopeType attribute temporarily to access the class and remove any remaining references, then deleted it again.
Despite all this, the error persists. It seems CMDBuild is still generating queries that include the deleted attribute.
Question:
Is there any internal configuration or cache that might still be referencing the old attribute? How can I fully reset or clean up the class configuration to stop this error?
Any help would be greatly appreciated.
Thank you!