You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Marco Risaliti (JIRA)" <ji...@apache.org> on 2007/12/20 17:46:43 UTC
[jira] Updated: (OFBIZ-330) problems displaying UOMs in the fixed
asset screen when using hsql
[ https://issues.apache.org/jira/browse/OFBIZ-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marco Risaliti updated OFBIZ-330:
---------------------------------
Component/s: (was: accounting)
INCORPORATING ISSUE
> problems displaying UOMs in the fixed asset screen when using hsql
> ------------------------------------------------------------------
>
> Key: OFBIZ-330
> URL: https://issues.apache.org/jira/browse/OFBIZ-330
> Project: OFBiz
> Issue Type: Bug
> Components: INCORPORATING ISSUE
> Environment: Database: HSQL
> Reporter: Ricardo Chavez
> Priority: Minor
>
> Hello everybody. I've encoutered the following problems when working with the default database manager (HSQL):
> When editing or creating a new fixed asset, the UOM and CommonCalendar drop-down fields don't show any elements. Upon examinig the log, I've found the following:
> 2006-09-26 10:51:05,984 (http-0.0.0.0-8443-Processor4) [ GenericDelegator.java:1713:ERROR]
> ---- exception report ----------------------------------------------------------
> Failure in findByCondition operation for entity [UomAndType]: org.ofbiz.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT UOM.UOM_ID AS UOM_ID, UOM.UOM_TYPE_ID AS UOM_TYPE_ID, UOM.ABBREVIATION AS ABBREVIATION, UOM.DESCRIPTION AS DESCRIPTION, UOMTP.UOM_TYPE_ID AS TYPE_UOM_TYPE_ID, UOMTP.PARENT_TYPE_ID AS TYPE_PARENT_TYPE_ID, UOMTP.HAS_TABLE AS TYPE_HAS_TABLE, UOMTP.DESCRIPTION AS TYPE_DESCRIPTION FROM UOM UOM INNER JOIN UOM_TYPE UOMTP ON UOM.UOM_TYPE_ID = UOMTP.UOM_TYPE_ID ORDER BY UOM_TYPE_ID ASC (ambiguous Column reference: UOM_TYPE_ID in statement [... (same statement as above) ...]). Rolling back transaction.
> (etc., etc.)
> Switching to Derby fixes the problem, which leads me to think it's a problem with HSQL.
> Regards,
> -- Ricardo Chavez
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.