Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | ||||||||
0030488 | ||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
defect | [Openbravo ERP] A. Platform | minor | have not tried | 2015-08-04 09:21 | 2015-11-11 12:16 | |||
Reporter | AugustoMauch | View Status | public | |||||
Assigned To | platform | |||||||
Priority | normal | Resolution | suspended | Fixed in Version | ||||
Status | closed | Fix in branch | Fixed in SCM revision | |||||
Projection | none | ETA | none | Target Version | ||||
OS | Any | Database | Any | Java version | ||||
OS Version | Database version | Ant version | ||||||
Product Version | SCM revision | |||||||
Review Assigned To | ||||||||
Web browser | ||||||||
Modules | Core | |||||||
Regression level | ||||||||
Regression date | ||||||||
Regression introduced in release | ||||||||
Regression introduced by commit | ||||||||
Triggers an Emergency Pack | No | |||||||
Summary | 0030488: API Change: Replacement of LOWER with UPPER in queries | |||||||
Description | In order to solve this feature request [1], all instances of the LOWER function in SQL queries throughout the Openbravo codebase are going to be replaced with upper. It is going to be done ensuring that the results returned by the queries does not change, but it is possible that some of those queries could take more time to execute for users that have defined function based indexes using the lower function, thus this change can be considered somewhat of an API change. Note that Openbravo will not start giving support to function based indexes until PR15Q4, so if someone had defined those indexes, they would have to maintain them themselves (there was no way to export/import them) [1] https://issues.openbravo.com/view.php?id=30476 [^] | |||||||
Steps To Reproduce | - | |||||||
Tags | Approved | |||||||
Attached Files | ||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | |||||||||||||||
|
Notes | |
(0079198) dmitry_mezentsev (developer) 2015-08-05 12:10 |
Augusto, I think it also makes sense to communicate to staff.engineering not just only this API change but the rule to use UPPER with LOWER being "on special and clear request / demand". IMHO we should think on a place to reflect the same in the Dev. Guide even. |
(0081696) alostale (manager) 2015-11-11 12:16 |
There is no plan for the moment to do this change |
Issue History | |||
Date Modified | Username | Field | Change |
2015-08-04 09:21 | AugustoMauch | New Issue | |
2015-08-04 09:21 | AugustoMauch | Assigned To | => dmitry_mezentsev |
2015-08-04 09:21 | AugustoMauch | Modules | => Core |
2015-08-04 09:21 | AugustoMauch | Triggers an Emergency Pack | => No |
2015-08-04 09:22 | AugustoMauch | Relationship added | related to 0030476 |
2015-08-05 12:07 | dmitry_mezentsev | Tag Attached: Approved | |
2015-08-05 12:07 | dmitry_mezentsev | Assigned To | dmitry_mezentsev => AugustoMauch |
2015-08-05 12:10 | dmitry_mezentsev | Note Added: 0079198 | |
2015-08-12 14:57 | AugustoMauch | Relationship added | related to 0030561 |
2015-11-10 15:02 | alostale | Status | new => acknowledged |
2015-11-11 12:13 | alostale | Assigned To | AugustoMauch => platform |
2015-11-11 12:16 | alostale | Status | acknowledged => scheduled |
2015-11-11 12:16 | alostale | Note Added: 0081696 | |
2015-11-11 12:16 | alostale | Status | scheduled => closed |
2015-11-11 12:16 | alostale | Resolution | open => suspended |
Copyright © 2000 - 2009 MantisBT Group |