[opencms-dev] OpenCms SQL Statement error (PostgreSQL 8.3.3)

[Michael Moossen]

Hi Roman!

update to OpenCms 7.0.5, since this has been fixed in OpenCms 7.0.4

Kind regards,
Michael

-------------------

Alkacon Software GmbH  - The OpenCms Experts
http://www.alkacon.com - http://www.opencms.org


Roman Uhlig wrote:
> After upgrading from PostgreSQL 8.2.7 to 8.3.3 we always get the following
> OpenCms SQL statement error when trying to publish resources:
> 
> Error reading the direct publish list for resource "/monitoring/".
> Reason: An SQL error occurred when executing the following query: SELECT
> CMS_OFFLINE_STRUCTURE.STRUCTURE_ID,CMS_OFFLINE_STRUCTURE.RESOURCE_ID,CMS_OFFLINE_STRUCTURE.RESOURCE_PATH,CMS_OFFLINE_STRUCTURE.STRUCTURE_STATE,CMS_OFFLINE_STRUCTURE.DATE_RELEASED,CMS_OFFLINE_STRUCTURE.DATE_EXPIRED,CMS_OFFLINE_RESOURCES.RESOURCE_ID,CMS_OFFLINE_RESOURCES.RESOURCE_TYPE,CMS_OFFLINE_RESOURCES.RESOURCE_FLAGS,CMS_OFFLINE_RESOURCES.RESOURCE_STATE,CMS_OFFLINE_RESOURCES.DATE_CREATED,CMS_OFFLINE_RESOURCES.DATE_LASTMODIFIED,CMS_OFFLINE_RESOURCES.USER_CREATED,CMS_OFFLINE_RESOURCES.USER_LASTMODIFIED,CMS_OFFLINE_RESOURCES.PROJECT_LASTMODIFIED
> AS
> LOCKED_IN_PROJECT,CMS_OFFLINE_RESOURCES.RESOURCE_SIZE,CMS_OFFLINE_RESOURCES.SIBLING_COUNT,CMS_OFFLINE_RESOURCES.PROJECT_LASTMODIFIED
> FROM CMS_OFFLINE_STRUCTURE INNER JOIN CMS_OFFLINE_RESOURCES ON
> CMS_OFFLINE_STRUCTURE.RESOURCE_ID=CMS_OFFLINE_RESOURCES.RESOURCE_ID AND
> (CMS_OFFLINE_RESOURCES.PROJECT_LASTMODIFIED=4) AND
> (CMS_OFFLINE_RESOURCES.RESOURCE_SIZE = -1) AND
> (CMS_OFFLINE_STRUCTURE.RESOURCE_PATH LIKE /sites/default/monitoring/% ESCAPE
> '|') AND NOT (((CMS_OFFLINE_STRUCTURE.STRUCTURE_STATE=0 AND
> CMS_OFFLINE_STRUCTURE.STRUCTURE_STATE >=
> CMS_OFFLINE_RESOURCES.RESOURCE_STATE) OR
> (CMS_OFFLINE_RESOURCES.RESOURCE_STATE=0 AND
> CMS_OFFLINE_RESOURCES.RESOURCE_STATE >=
> CMS_OFFLINE_STRUCTURE.STRUCTURE_STATE))) ORDER BY
> CMS_OFFLINE_STRUCTURE.RESOURCE_PATH.
> Reason: ERROR: operator does not exist: smallint = character varying
> 
> 
> Is there possibly any solution to this or do we have to downgrade to
> PostgreSQL 8.2.7 again?
> 
> Thanks in advance for any help,
> Roman