Project:
| View Revisions: Issue #47831 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0047831: Problem introducing long descriptions in some tables (CORE) | ||
| Revision | 2021-10-11 10:19 by fernando_merino | ||
| Description | This problem occurs only on an Oracle database. The problem is that the DESCRIPTION field, of some core 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 core affected: M_INVENTORYSTATUS_TRL C_PERIODCONTROL_LOG FIN_PAYMENTMETHOD AD_APPLICATION FIN_PAYMENT_PROPOSAL C_TAXREGISTER_TYPE C_DP_MANAGEMENT FIN_PAYMENT_SCHEDULE M_OFFER AD_PROCESS_REQUEST M_OFFER_TYPE M_INVENTORYSTATUS C_REJECT_REASON C_SETTLEMENT AD_ORGTYPE FIN_DOUBTFUL_DEBT_METHOD M_OFFER_TYPE_TRL M_REFINVENTORY_TYPE AD_PROCESS_GROUP OBUIAPP_PROCESS_TRL (Module: org.openbravo.client.application) OBUIAPP_MENU_PARAMETERS (Module: org.openbravo.client.application) OBUIAPP_VIEW_IMPL (Module: org.openbravo.client.application) OBUIAPP_NAVBAR_COMPONENT (Module: org.openbravo.client.application) OBUIAPP_PROCESS (Module: org.openbravo.client.application) |
||
| Revision | 2021-10-11 10:07 by fernando_merino | ||
| Description | This problem occurs only on an Oracle database. The problem is that the DESCRIPTION field, of some core 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 core affected: M_INVENTORYSTATUS_TRL C_PERIODCONTROL_LOG FIN_PAYMENTMETHOD AD_APPLICATION FIN_PAYMENT_PROPOSAL C_TAXREGISTER_TYPE C_DP_MANAGEMENT FIN_PAYMENT_SCHEDULE M_OFFER AD_PROCESS_REQUEST M_OFFER_TYPE M_INVENTORYSTATUS C_REJECT_REASON C_SETTLEMENT AD_ORGTYPE FIN_DOUBTFUL_DEBT_METHOD M_OFFER_TYPE_TRL M_REFINVENTORY_TYPE AD_PROCESS_GROUP OBUIAPP_PROCESS_TRL OBUIAPP_MENU_PARAMETERS OBUIAPP_VIEW_IMPL OBUIAPP_NAVBAR_COMPONENT OBUIAPP_PROCESS |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |