Details
-
Bug
-
Resolution: Fixed
-
Medium
-
3.13.4
-
Postgres
-
3.13
-
Description
When JIRA is connected to Postgres 8.3+ you cannot:
- Delete an external Gadget from the gadget directory.
- Delete an option from a cascading select custom field.
- ... (I am sure there are others).
JIRA will not work with Postgres 8.3 or higher. Users will encounter errors like:
SEVERE: Internal server error com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: Generic Entity Exception occurred in deleteByAnd (SQL Exception while executing the following:DELETE FROM public.externalgadget WHERE ID=? (ERROR: operator does not exist: numeric = character varying Hint: No operator matches the given name and argument type(s). You might need to add explicit type casts.
I found this bug in Postgres:
http://archives.postgresql.org/pgsql-bugs/2008-04/msg00003.php
It pointed me to the release notes where it looks like a an intentional design change to require explicit type casts.
Attachments
Issue Links
- is duplicated by
-
JRASERVER-20337 Can't remove gadget from Gadget Directory
- Closed
- is related to
-
JRASERVER-67234 OfBiz operations fail with "ERROR: operator does not exist" when JIRA is connected to Postgres
- Gathering Impact
-
JRASERVER-71249 Deleting a custom field fails with "No operator matches the given name and argument type" when JIRA is connected to Postgres
- Gathering Impact
- relates to
-
DEVHELP-1178 Loading...