Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0004757Openbravo ERPY. DBSourceManagerpublic2008-08-29 11:522009-03-18 11:02
Reporteriperdomo 
Assigned Tomarvintm 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS20OS Version2.6.23-gentoo-r9
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0004757: Create database fails on PostgreSQL due to some varchar2 dataypes
DescriptionThe stored procedures are not *well* translated and tries to use varchar2 as datatype.

A issue was open in Openbravo ERP project:
https://issues.openbravo.com/view.php?id=4643 [^]
Steps To Reproduce
Proposed Solution
Additional Information
Tagsdbsm_migrate
Relationships
blocks defect 00046432.50 closed cromero ant create.database fails with postgresql-8.3 after merge of uuid-branch to r2.5x 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2008-08-29 11:52iperdomoNew Issue
2008-08-29 11:55iperdomoRelationship addedrelated to 0004643
2008-08-29 11:55iperdomoRelationship deletedrelated to 0004643
2008-08-29 11:55iperdomoRelationship addedblocks 0004643
2008-09-01 15:41marvintmStatusnew => scheduled
2008-09-01 15:41marvintmAssigned To => marvintm
2008-09-01 15:41marvintmfix_in_branch => trunk
2008-09-01 15:43marvintmStatusscheduled => resolved
2008-09-01 15:43marvintmResolutionopen => fixed
2008-09-01 15:43marvintmNote Added: 0008828
2008-11-25 23:35psarobeStatusresolved => closed
2008-12-18 12:38jpabloaeSticky IssueNo => Yes
2008-12-18 12:39jpabloaeSticky IssueYes => No
2008-12-18 12:39jpabloaeTag Attached: dbsm_migrate
2008-12-18 12:41jpabloaeProject@4@ => Openbravo ERP
2008-12-18 12:41jpabloaeCategory => Y. DBSourceManager
2009-03-18 11:02anonymoussf_bug_id0 => 2691346

Notes
(0008828)
marvintm   
2008-09-01 15:43   
This was fixed by changing the VARCHAR2 variables to VARCHAR ones in the Openbravo trunk, no change was necessary in dbsourcemanager.