Project:
View Revisions: Issue #47832 | [ All Revisions ] [ Back to Issue ] | ||
Summary | 0047832: Problem introducing long descriptions in some tables (Retail Pack Modules) | ||
Revision | 2021-10-11 10:41 by fernando_merino | ||
Description | This problem occurs only on an Oracle database. The problem is that the DESCRIPTION field, of some retail modules tables listed below, is defined as VARCHAR2(255 BYTE). The DESCRIPTION field is limited to 255 CHARACTERS long, so if all these characters don't exceed the limit of 255 BYTES there is no problem (e.g 255 characters of 1 BYTE each). The problem comes when the description contains characters larger than 1 BYTE. If the description is a long one, for example one with 255 characters, the characters limit is not exceeded, but if it contains some characters larger than 1 BYTE, like for example the º character that occupies 2 BYTES, then the limit of 255 BYTES is exceeded (254 one-byte characters, plus one of 2 bytes make 256 bytes, which do not fit in the field defined in the database). I indicate below all the tables from retail pack modules affected: org.openbravo.retail.config --> OBRETCO_PRODUCTLIST org.openbravo.retail.posterminal --> OBPOS_APPROVAL_REASON org.openbravo.retail.posterminal --> OBPOS_PAYMENTGROUP_TRL org.openbravo.retail.posterminal --> OBPOS_PAYMENTGROUP org.openbravo.mobile.core --> OBMOBC_ABA org.openbravo.mobile.core --> OBMOBC_PROCESS_DEFINITION org.openbravo.mobile.core --> OBMOBC_ACTION org.openbravo.mobile.core --> OBMOBC_ABA_LAYVARIANT org.openbravo.mobile.core --> OBMOBC_UICONFIGURATION org.openbravo.mobile.core --> OBMOBC_WINDOW |
||
Revision | 2021-10-11 10:39 by fernando_merino | ||
Description | This problem occurs only on an Oracle database. The problem is that the DESCRIPTION field, of some retail modules tables listed below, is defined as VARCHAR2(255 BYTE). The DESCRIPTION field is limited to 255 CHARACTERS long, so if all these characters don't exceed the limit of 255 BYTES there is no problem (e.g 255 characters of 1 BYTE each). The problem comes when the description contains characters larger than 1 BYTE. If the description is a long one, for example one with 255 characters, the characters limit is not exceeded, but if it contains some characters larger than 1 BYTE, like for example the º character that occupies 2 BYTES, then the limit of 255 BYTES is exceeded (254 one-byte characters, plus one of 2 bytes make 256 bytes, which do not fit in the field defined in the database). I indicate below all the tables from retail pack modules affected: org.openbravo.retail.config OBRETCO_PRODUCTLIST org.openbravo.retail.posterminal OBPOS_APPROVAL_REASON org.openbravo.retail.posterminal OBPOS_PAYMENTGROUP_TRL org.openbravo.retail.posterminal OBPOS_PAYMENTGROUP org.openbravo.mobile.core OBMOBC_ABA org.openbravo.mobile.core OBMOBC_PROCESS_DEFINITION org.openbravo.mobile.core OBMOBC_ACTION org.openbravo.mobile.core OBMOBC_ABA_LAYVARIANT org.openbravo.mobile.core OBMOBC_UICONFIGURATION org.openbravo.mobile.core OBMOBC_WINDOW |
Copyright © 2000 - 2009 MantisBT Group |