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

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0005197
TypeCategorySeverityReproducibilityDate SubmittedLast Update
backport[Openbravo ERP] 00. Application dictionarymajoralways2008-09-23 13:012009-01-26 10:41
ReportergalderromoView Statuspublic 
Assigned Toalostale 
PriorityimmediateResolutionfixedFixed in Version
StatusclosedFix in branch2.3xFixed in SCM revision11163
ProjectionnoneETAnoneTarget Version
OSLinux 32 bitDatabaseOracleJava version1.5.0_15
OS VersionGentoo 2.6.24Database versionXEAnt version1.7
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

0005197: Doc sequences and database restrictions

DescriptionRight now, when working with Sales Invoices, WAD generated code updates the document's sequence before is sure the invoice has been created. This way it is possible to update the sequence but not to create the record due to database restrictions.

This issue is critica because can generate sequence jumps on Sales Invoices, which is ilegal.

In some how, this request is related to 4439 and 5054.
Steps To ReproduceSuppose you do not want the user to create an invoice with no c_project_id or not user1_id. So you create on the database this restriction (there is no way to do it through the AP).

Then, when you press the SAVE button, the WAD generated code updates the sequence and later inserts the record on the database. But the restriction avoids this inserting, so the sequence has been lost.
Proposed SolutionChange the sequence control, and make sure the inserting has been properly done, before updating the sequence.
TagsNo tags attached.
Attached Files

- Relationships [ Relation Graph ] [ Dependency Graph ]
blocks defect 0005175 closedalostale Doc sequences and database restrictions 

-  Notes
(0010851)
svnbot (reporter)
2008-12-01 17:20

 Repository: openbravo
Revision: 10801
Author: alostale
Date: 2008-12-01 17:20:26 +0100 (Mon, 01 Dec 2008)

fixed bug 0005197: Doc sequences and database restrictions

---
U branches/r2.3x/src/org/openbravo/erpCommon/utility/DocumentNo_data.xsql
U branches/r2.3x/src/org/openbravo/erpCommon/utility/Utility.java
U branches/r2.3x/src-wad/src/org/openbravo/wad/Wad.java
U branches/r2.3x/src-wad/src/org/openbravo/wad/datasource.xsqlxml
U branches/r2.3x/src-wad/src/org/openbravo/wad/javasource.javaxml
---

https://dev.openbravo.com/websvn/openbravo/?rev=10801&sc=1 [^]
(0011255)
svnbot (reporter)
2008-12-12 16:13

 Repository: openbravo
Revision: 11163
Author: rafaroda
Date: 2008-12-12 16:13:04 +0100 (Fri, 12 Dec 2008)

Fixes bug 0005197 Made fix PotgreSQL compatible

---
U branches/r2.3x/src/org/openbravo/erpCommon/utility/DocumentNo_data.xsql
---

https://dev.openbravo.com/websvn/openbravo/?rev=11163&sc=1 [^]

- Issue History
Date Modified Username Field Change
2008-09-23 13:01 cromero New Issue
2008-09-23 13:01 cromero Assigned To => alostale
2008-09-23 13:01 cromero Status new => scheduled
2008-12-01 11:17 networkb Issue Monitored: networkb
2008-12-01 11:17 networkb Priority high => immediate
2008-12-01 17:20 svnbot Checkin
2008-12-01 17:20 svnbot Note Added: 0010851
2008-12-01 17:20 svnbot Status scheduled => resolved
2008-12-01 17:20 svnbot Resolution open => fixed
2008-12-01 17:20 svnbot svn_revision => 10801
2008-12-12 16:13 svnbot Checkin
2008-12-12 16:13 svnbot Note Added: 0011255
2008-12-12 16:13 svnbot svn_revision 10801 => 11163
2008-12-12 17:52 psarobe Status resolved => new
2008-12-12 17:52 psarobe Resolution fixed => open
2008-12-12 17:52 psarobe Fixed in Version 2.35MP10 =>
2008-12-12 17:52 psarobe Status new => scheduled
2008-12-12 17:52 psarobe Status scheduled => resolved
2008-12-12 17:52 psarobe Resolution open => fixed
2009-01-26 10:41 psarobe Regression testing => No
2009-01-26 10:41 psarobe Status resolved => closed

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker