Confusion in entity engine if schema is named prod (and probably other table name prefixes)
------------------------------------------------------------------------------------------- Key: OFBIZ-778 URL: https://issues.apache.org/jira/browse/OFBIZ-778 Project: OFBiz (The Open for Business Project) Issue Type: Bug Components: framework Reporter: Eriks Dobelis Priority: Trivial I checked out fresh version from SVN today, and started to get lines like these in console.log for all prod_* tables. 2007-03-05 22:05:42,156 (main) [ DatabaseUtil.java:351:WARN ] Entity [ProdCatalogCategory] has no table in the database 2007-03-05 22:05:42,158 (main) [ DatabaseUtil.java:359:ERROR] Could not create table [prod.PROD_CATALOG_CATEGORY]: SQL Exception while executing the following: CREATE TABLE prod.PROD_CATALOG_CATEGORY (PROD_CATALOG_ID VARCHAR(20) NOT NULL, PRODUCT_CATEGORY_ID VARCHAR(20) NOT NULL, PROD_CATALOG_CATEGORY_TYPE_ID VARCHAR(20) NOT NULL, FROM_DATE TIMESTAMPTZ NOT NULL, THRU_DATE TIMESTAMPTZ, SEQUENCE_NUM NUMERIC(18,0), LAST_UPDATED_STAMP TIMESTAMPTZ, LAST_UPDATED_TX_STAMP TIMESTAMPTZ, CREATED_STAMP TIMESTAMPTZ, CREATED_TX_STAMP TIMESTAMPTZ, CONSTRAINT PK_PROD_CATALOG_CATEGORY PRIMARY KEY (PROD_CATALOG_ID, PRODUCT_CATEGORY_ID, PROD_CATALOG_CATEGORY_TYPE_ID, FROM_DATE)) Error was: org.postgresql.util.PSQLException: ERROR: relation "prod_catalog_category" already exists Table actually exists in the database. Coincidence is that I named schema "prod", which probably is the reason for confusion for entity engine. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
[ https://issues.apache.org/jira/browse/OFBIZ-778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552153 ] Marco Risaliti commented on OFBIZ-778: -------------------------------------- Hi Eriks, have you try with a recent version from trunk if this is an old issue and now it has been solved ? If it's not the case can you upload a new full console.log ? Thanks Marco > Confusion in entity engine if schema is named prod (and probably other table name prefixes) > ------------------------------------------------------------------------------------------- > > Key: OFBIZ-778 > URL: https://issues.apache.org/jira/browse/OFBIZ-778 > Project: OFBiz > Issue Type: Bug > Components: framework > Reporter: Eriks Dobelis > Priority: Trivial > > I checked out fresh version from SVN today, and started to get lines like these in console.log for all prod_* tables. > 2007-03-05 22:05:42,156 (main) [ DatabaseUtil.java:351:WARN ] Entity [ProdCatalogCategory] has no table in the database > 2007-03-05 22:05:42,158 (main) [ DatabaseUtil.java:359:ERROR] Could not create table [prod.PROD_CATALOG_CATEGORY]: SQL Exception while executing the following: > CREATE TABLE prod.PROD_CATALOG_CATEGORY (PROD_CATALOG_ID VARCHAR(20) NOT NULL, PRODUCT_CATEGORY_ID VARCHAR(20) NOT NULL, PROD_CATALOG_CATEGORY_TYPE_ID VARCHAR(20) NOT NULL, FROM_DATE TIMESTAMPTZ NOT NULL, THRU_DATE TIMESTAMPTZ, SEQUENCE_NUM NUMERIC(18,0), LAST_UPDATED_STAMP TIMESTAMPTZ, LAST_UPDATED_TX_STAMP TIMESTAMPTZ, CREATED_STAMP TIMESTAMPTZ, CREATED_TX_STAMP TIMESTAMPTZ, CONSTRAINT PK_PROD_CATALOG_CATEGORY PRIMARY KEY (PROD_CATALOG_ID, PRODUCT_CATEGORY_ID, PROD_CATALOG_CATEGORY_TYPE_ID, FROM_DATE)) > Error was: org.postgresql.util.PSQLException: ERROR: relation "prod_catalog_category" already exists > Table actually exists in the database. Coincidence is that I named schema "prod", which probably is the reason for confusion for entity engine. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
Free forum by Nabble | Edit this page |