Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | ||||||||||||
| 0047831 | ||||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| design defect | [Openbravo ERP] Z. Others | major | always | 2021-10-11 10:07 | 2021-10-15 11:18 | |||||||
| Reporter | fernando_merino | View Status | public | |||||||||
| Assigned To | Triage Omni OMS | |||||||||||
| Priority | normal | Resolution | open | Fixed in Version | ||||||||
| Status | new | Fix in branch | Fixed in SCM revision | |||||||||
| Projection | none | ETA | none | Target Version | ||||||||
| OS | Any | Database | Oracle | Java version | ||||||||
| OS Version | Database version | Ant version | ||||||||||
| Product Version | main | SCM revision | ||||||||||
| Review Assigned To | ||||||||||||
| Web browser | Google Chrome | |||||||||||
| Modules | Core | |||||||||||
| Regression level | ||||||||||||
| Regression date | ||||||||||||
| Regression introduced in release | ||||||||||||
| Regression introduced by commit | ||||||||||||
| Triggers an Emergency Pack | No | |||||||||||
| Summary | 0047831: Problem introducing long descriptions in some tables (CORE) | |||||||||||
| 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) | |||||||||||
| Steps To Reproduce | 1. Go to any window that makes use of some of the tables listed above (e.g Payment Method window for the FIN_PAYMENTMETHOD table) 2. Create a new record and in the DESCRIPTION field input a long description reaching the limit of 255 characters and containing some characters larger than 1 BYTE, like for example the º characters. (Try with this description for example: This is a description example:ººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººººº) 3. Try to save the record, you will get an error similar to this one: ERROR: Saving failed. ORA-12899: value too large for column "ERP_PI_ORACLE"."FIN_PAYMENTMETHOD"."DESCRIPTION" (actual: 480, maximum: 255) | |||||||||||
| Proposed Solution | 1. Change column definition of the DESCRIPTION field from VARCHAR to NVARCHAR for all the tables affected | |||||||||||
| Tags | No tags attached. | |||||||||||
| Attached Files |  AffectedTables.png [^] (64,762 bytes) 2021-10-11 10:22
| |||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|||||||||||||||||
|
|||||||||||||||||
 Relationships |
|
Notes |
|
| There are no notes attached to this issue. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2021-10-11 10:07 | fernando_merino | New Issue | |
| 2021-10-11 10:07 | fernando_merino | Assigned To | => Triage Finance |
| 2021-10-11 10:07 | fernando_merino | File Added: TablesAffected.png | |
| 2021-10-11 10:07 | fernando_merino | Web browser | => Google Chrome |
| 2021-10-11 10:07 | fernando_merino | Modules | => Core |
| 2021-10-11 10:07 | fernando_merino | Triggers an Emergency Pack | => No |
| 2021-10-11 10:19 | fernando_merino | Web browser | Google Chrome => Google Chrome |
| 2021-10-11 10:19 | fernando_merino | Description Updated | View Revisions |
| 2021-10-11 10:20 | fernando_merino | File Added: AffectedTables.png | |
| 2021-10-11 10:20 | fernando_merino | File Deleted: TablesAffected.png | |
| 2021-10-11 10:21 | fernando_merino | Web browser | Google Chrome => Google Chrome |
| 2021-10-11 10:22 | fernando_merino | File Deleted: AffectedTables.png | |
| 2021-10-11 10:22 | fernando_merino | File Added: AffectedTables.png | |
| 2021-10-11 13:29 | fernando_merino | Relationship added | related to 0047765 |
| 2021-10-11 13:29 | fernando_merino | Relationship added | related to 0047832 |
| 2021-10-15 11:18 | aferraz | Web browser | Google Chrome => Google Chrome |
| 2021-10-15 11:18 | aferraz | Type | defect => design defect |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |