|
Notes |
|
|
|
|
Note: as explained by alostale looks like a technical necessity (oracle can only have 30 character object names) now enforced in by our model. |
|
|
|
|
AD_Process.ProcedureName column is used to store the PL/SQL procedure name implementing a process. As DB objects in Oracle cannot be longer than 30 characters, and DBSourceManager truncates actual procedure names to 30 characters, it is useless to be able to introduce longer procedure names in this column.
Furthermore, it is error prone, as happened in issue 0012103. It is possible that the procedure name in AD to be longer than 30 characters and when exporting from PG this name is truncated, if the developer does not notice the process will not work the next time database is updated. |
|
|
|
(0024094)
|
|
hgbot
|
|
2010-02-10 13:11
|
|
Repository: erp/devel/pi
Changeset: fd9d74a9c8cf9db187b19f4805c89f341239a6b3
Author: Asier Lostalé <asier.lostale <at> openbravo.com>
Date: Wed Feb 10 13:12:53 2010 +0100
URL: http://code.openbravo.com/erp/devel/pi/rev/fd9d74a9c8cf9db187b19f4805c89f341239a6b3 [^]
related to issue 12103, related to issue 12193
Rollback physical column size change done in previous commit, as it introduces an
error when updating database
---
M src-db/database/model/tables/AD_PROCESS.xml
---
|
|
|
|
|
This column has been changed back to 60 character long in DB, but in AD is kept as 30. In this way it will not be possible to enter longer names by UI.
Being 30 in DB caused error messages in update.database though the process completed successfully. |
|
|
|
|
|