Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0000382
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] Y. DBSourceManagermajoralways2008-05-20 16:162009-03-18 11:02
ReportermarvintmView Statuspublic 
Assigned Tomarvintm 
PriorityhighResolutionfixedFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabasePostgreSQLJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0000382: Export.database doesn't work in PostgreSQL (Invalid property name 'CODE_REVISION')

DescriptionWhen you try to export structure or data in PostgreSQL in the Trunk, it gives an error:

export.database:

export.database.structure:
[exportdatabase] Reading tables...
[exportdatabase] Reading views...
[exportdatabase] Reading sequences...
[exportdatabase] Reading triggers...
[exportdatabase] Reading functions...
[exportdatabase] Sorting foreign keys and checks...
[exportdatabase] Starting function and trigger standardization.

BUILD FAILED
/home/openbravo/workspaceBuena/openbravo/build.xml:298: The following error occurred while executing this line:
/home/openbravo/workspaceBuena/openbravo/src-db/database/build.xml:355: java.lang.IllegalArgumentException: Invalid property name 'CODE_REVISION'

The problem is that in PostgreSQL, properties have to be searched in beans in lower case, and DBSourceManager currently searches the property CODE_REVISION in upper case.
Steps To ReproduceJust do

ant export.database

in a working copy of the trunk, with Openbravo.properties pointing to a PostgreSQL database.
Tagsdbsm_migrate
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0000259)
marvintm (developer)
2008-05-20 16:17

It only happens in the trunk (in 2.3x and in 2.4x the security mechanism for DBSourceManager wasn't yet implemented).
(0000285)
marvintm (developer)
2008-05-21 12:11

Now export.database will work again in PostgreSQL.

- Issue History
Date Modified Username Field Change
2008-05-20 16:16 marvintm New Issue
2008-05-20 16:16 marvintm Assigned To => marvintm
2008-05-20 16:17 marvintm Status new => scheduled
2008-05-20 16:17 marvintm Note Added: 0000259
2008-05-21 12:11 marvintm Status scheduled => resolved
2008-05-21 12:11 marvintm Resolution open => fixed
2008-05-21 12:11 marvintm Note Added: 0000285
2008-11-26 14:10 psarobe Status resolved => closed
2008-12-18 12:38 jpabloae Sticky Issue No => Yes
2008-12-18 12:39 jpabloae Sticky Issue Yes => No
2008-12-18 12:39 jpabloae Tag Attached: dbsm_migrate
2008-12-18 12:41 jpabloae Project @4@ => Openbravo ERP
2008-12-18 12:41 jpabloae Category => Y. DBSourceManager
2009-03-18 11:02 anonymous sf_bug_id 0 => 2691308


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker