Openbravo Issue Tracking System - Openbravo ERP |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0006211 | Openbravo ERP | 00. Application dictionary | public | 2008-11-26 14:06 | 2008-12-11 14:55 |
|
| Reporter | networkb | |
| Assigned To | pheenan | |
| Priority | immediate | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | |
| Platform | | OS | 5 | OS Version | |
| Product Version | 2.35MP9 | |
| Target Version | | Fixed in Version | | |
| Merge Request Status | |
| Review Assigned To | |
| OBNetwork customer | OBPS |
| Web browser | |
| Modules | Core |
| Support ticket | |
| Regression level | |
| Regression date | |
| Regression introduced in release | |
| Regression introduced by commit | |
| Triggers an Emergency Pack | No |
|
| Summary | 0006211: If you fill a field with the maximum length permited and one of the character is special it fails when saving |
| Description | If you fill a field with the maximum length permitted and one of the character is special, you get the following error:
ORA-12899: value too large for column "TAD_BRANCH_R23X_DEMO"."M_PRODUCT"."UPC" (actual: 31, maximum: 30)
|
| Steps To Reproduce | 1-Go to the product window
2-Fill the upc field with
ppppppppppppppppppppppppppppp (30 characcteres)
3-Save.
4- You get the error.
|
| Proposed Solution | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | | related to | defect | 0006390 | | closed | pheenan | Rpt_Etiquetas_data.xsql does not compile | | related to | backport | 0006505 | 2.35 | closed | pheenan | Backport issue 6211: 0006211: If you fill a field with the maximum length permited and one of the character is special it fails | | related to | backport | 0006507 | 2.40 | closed | pheenan | Backport issue 6211: 0006211: If you fill a field with the maximum length permited and one of the character is special it fails |
|
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2008-11-26 14:06 | networkb | New Issue | |
| 2008-11-26 14:06 | networkb | Assigned To | => rafaroda |
| 2008-11-26 14:06 | networkb | sf_bug_id | 0 => 2350781 |
| 2008-11-26 14:06 | networkb | OBNetwork customer | => Yes |
| 2008-11-26 14:06 | networkb | Regression testing | => No |
| 2008-11-26 14:42 | pjuvara | Sticky Issue | No => Yes |
| 2008-11-26 14:42 | pjuvara | Sticky Issue | Yes => No |
| 2008-11-26 17:57 | rafaroda | Note Added: 0010735 | |
| 2008-11-26 18:34 | rafaroda | Assigned To | rafaroda => pheenan |
| 2008-11-27 10:51 | pheenan | Status | new => scheduled |
| 2008-11-27 10:51 | pheenan | Note Added: 0010759 | |
| 2008-11-27 10:51 | pheenan | fix_in_branch | => trunk |
| 2008-11-27 19:19 | pnuding | Issue Monitored: pnuding | |
| 2008-12-05 12:52 | pheenan | Note Added: 0010997 | |
| 2008-12-05 17:19 | svnbot | Checkin | |
| 2008-12-05 17:19 | svnbot | Note Added: 0011005 | |
| 2008-12-05 17:19 | svnbot | Status | scheduled => resolved |
| 2008-12-05 17:19 | svnbot | Resolution | open => fixed |
| 2008-12-05 17:19 | svnbot | svn_revision | => 11008 |
| 2008-12-05 17:20 | svnbot | Checkin | |
| 2008-12-05 17:20 | svnbot | Note Added: 0011006 | |
| 2008-12-05 17:20 | svnbot | svn_revision | 11008 => 11009 |
| 2008-12-05 17:24 | svnbot | Checkin | |
| 2008-12-05 17:24 | svnbot | Note Added: 0011007 | |
| 2008-12-05 17:24 | svnbot | svn_revision | 11009 => 11010 |
| 2008-12-07 09:34 | jpabloae | Relationship added | related to 0006390 |
| 2008-12-11 14:55 | krishna | Status | resolved => closed |
| 2008-12-12 11:22 | pheenan | Relationship added | related to 0006505 |
| 2008-12-12 11:25 | pheenan | Relationship added | related to 0006507 |
|
Notes |
|
|
|
This issue has been tested both in Oracle and PostgreSQL.
In PostgreSQL it was not able to reproduce when testing in branch 2.3x, branch 2.40 and trunk.
In Oracle it was possible to reproduce in branch 2.3x, branch 2.40 and trunk. |
|
|
|
|
|
|
|
|
Having tested the possibility of changing the column to nvarchar this is not going to be a posible solution. The data becomes corrupted.
Proposed solution is to update DBSourceManager to cast string fields. This will be tested and confirmed before continuing with the modification to DBSourceManager. |
|
|
|
(0011005)
|
|
svnbot
|
|
2008-12-05 17:19
|
|
Repository: openbravo
Revision: 11008
Author: pheenan
Date: 2008-12-05 17:19:12 +0100 (Fri, 05 Dec 2008)
Fixed issue 6211. Updated columns to NVARCHAR from VARCHAR. This will enable the field to hold the maximum number of characters including special characters.
---
U trunk/src-db/database/model/tables/M_PRODUCT.xml
---
https://dev.openbravo.com/websvn/openbravo/?rev=11008&sc=1 [^]
|
|
|
|
(0011006)
|
|
svnbot
|
|
2008-12-05 17:20
|
|
Repository: openbravo
Revision: 11009
Author: pheenan
Date: 2008-12-05 17:20:48 +0100 (Fri, 05 Dec 2008)
Fixed issue 6211. Updated columns to NVARCHAR from VARCHAR. This will enable the field to hold the maximum number of characters including special characters.
---
U branches/r2.3x/database/model/tables/M_PRODUCT.xml
---
https://dev.openbravo.com/websvn/openbravo/?rev=11009&sc=1 [^]
|
|
|
|
(0011007)
|
|
svnbot
|
|
2008-12-05 17:24
|
|
Repository: openbravo
Revision: 11010
Author: pheenan
Date: 2008-12-05 17:24:25 +0100 (Fri, 05 Dec 2008)
Fixed issue 6211. Updated columns to NVARCHAR from VARCHAR. This will enable the field to hold the maximum number of characters including special characters.
---
U branches/r2.40/src-db/database/model/tables/M_PRODUCT.xml
---
https://dev.openbravo.com/websvn/openbravo/?rev=11010&sc=1 [^]
|
|