Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0002254Openbravo ERPK. Packagingpublic2007-11-11 15:182008-11-25 21:47
Reportervillind 
Assigned Tojpabloae 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionout of date 
PlatformOS5OS Version
Product Version 
Target Version3.0MP0Fixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0002254: The installer requires database superuser permissions
DescriptionThe installer requires database superuser permissions, as the openbravo application also this makes it impossible to use shared database server for openbravo and other applications, and the installer still can accidentally delete an existent database.

Steps To Reproduce
Proposed Solution
Additional Information
TagsReleaseCandidate
Relationships
depends on feature request 0004099 acknowledged iciordia Delete client should not drop constraints 
has duplicate feature request 00040792.50 closed jpabloae In both Oracle and PostgreSQL it should be possible to create the database with a given user and schema 
Not all the children of this issue are yet resolved or closed.
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2008-06-12 10:04jpabloaeProjectOpenbravo ERP => @5@
2008-06-12 11:56jpabloaeCategoryA.Installation & Platform => Installer
2008-06-19 17:44cromeroStatusnew => scheduled
2008-06-19 17:44cromeroAssigned Tojpabloae => marvintm
2008-06-21 00:32jpabloaeReporteruser11 => villind
2008-06-21 00:32jpabloaeTypedefect => feature request
2008-06-21 00:32jpabloaeDescription Updated
2008-06-21 00:34jpabloaeRelationship addeddepends on 0004099
2008-06-21 00:35jpabloaeAssigned Tomarvintm => jpabloae
2008-07-25 14:24jpabloaeRelationship addedhas duplicate 0004079
2008-09-08 15:54pjuvaraTag Attached: ReleaseCandidate
2008-09-08 15:55pjuvaraFixed in Versiontrunk =>
2008-09-08 15:58pjuvaraTarget Version => 2.60
2008-11-13 06:48jpabloaeStatusscheduled => closed
2008-11-13 06:48jpabloaeNote Added: 0010212
2008-11-13 06:48jpabloaeResolutionopen => out of date
2008-11-25 21:41pjuvaraSticky IssueNo => Yes
2008-11-25 21:43pjuvaraProject@5@ => Openbravo ERP
2008-11-25 21:45pjuvaraCategoryInstaller => K. Packaging
2008-11-25 21:47pjuvaraSticky IssueYes => No

Notes
(0005843)
user71   
2005-06-01 00:00   
(edited on: 2008-06-12 09:43)
This bug was originally reported in SourceForge bug tracker and then migrated to Mantis.

You can see the original bug report in:
https://sourceforge.net/support/tracker.php?aid=1829943 [^]
(0002641)
villind   
2007-11-11 21:59   
(edited on: 2008-06-12 09:23)
Logged In: YES
user_id=61737
Originator: NO

It would be nice if the Openbravo would behave as a normal application that just requires a database and the Openbravo installer could use an existing database (this is possible when installing from sources). The biggest issue at the moment is that the Openbravo modifies Postgresql system tables (pg_*) for disabling triggers and does not use ALTER TABLE syntax for that.

Related issues:
 * https://sourceforge.net/tracker/index.php?func=detail&aid=1761370&group_id=162271&atid=823132 [^]
 * https://sourceforge.net/tracker/index.php?func=detail&aid=1768416&group_id=162271&atid=823129 [^]
 * https://sourceforge.net/tracker/index.php?func=detail&aid=1822790&group_id=162271&atid=823132 [^]
(0010212)
jpabloae   
2008-11-13 06:48   
Thank you for the bug report.

However, I close the issue because we are not having an installer for 2.50 and future releases.