Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0008630 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| defect | [Openbravo ERP] 00. Application dictionary | minor | have not tried | 2009-04-18 11:30 | 2009-04-24 00:00 | |||
| Reporter | rentidee | View Status | public | |||||
| Assigned To | alostale | |||||||
| Priority | normal | Resolution | duplicate | Fixed in Version | ||||
| Status | closed | Fix in branch | Fixed in SCM revision | |||||
| Projection | none | ETA | none | Target Version | ||||
| OS | Linux 32 bit | Database | PostgreSQL | Java version | 1.6.0_11 | |||
| OS Version | rPath Linux | Database version | 8.3.5 | Ant version | 1.7.1 | |||
| Product Version | 2.50alpha-r11 | SCM revision | ||||||
| Merge Request Status | ||||||||
| Review Assigned To | ||||||||
| OBNetwork customer | No | |||||||
| Web browser | ||||||||
| Modules | Core | |||||||
| Support ticket | ||||||||
| Regression level | ||||||||
| Regression date | ||||||||
| Regression introduced in release | ||||||||
| Regression introduced by commit | ||||||||
| Triggers an Emergency Pack | No | |||||||
| Summary | 0008630: cannot switch module in tables and columns | |||||||
| Description | added new column to c_order table named the column according to the howto "create a new table 2.5". named the column EM_rent_rent_rentcontract_id as varchar(32) The column is supposed to be a relation to a table I created with the name rent_rentcontract primary key rent_rentcontract_id in a module named rent. That did work. The table c_order seemed to recognize the relation between the tables. But: when I try to switch the module of the column from core to rent (my module, because the column belongs not to base) I get an error stating "names must start with the table prefix". The howto says: Let's extend the existent HR_SALARY adding a new ValidTo column in a different module. Let's suppose that we already have a module and its DBPrefix is HR2'. In this case the name of the column must be like EM_HR2_VALIDTO, EM stands for External Module, HR2 is the external module's DBPrefix, and finally we add the desired name for the column. | |||||||
| Steps To Reproduce | Adding a new column to an existing core table with a name starting with EM_ should do the trick | |||||||
| Proposed Solution | change the constraint causing the error message or change the howto. Maybe EM is not required for adding columns to an existing table. | |||||||
| Tags | Modularity | |||||||
| Attached Files | ||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
||||||||
|
||||||||
 Relationships |
|
Notes |
|
| There are no notes attached to this issue. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2009-04-18 11:30 | rentidee | New Issue | |
| 2009-04-18 11:30 | rentidee | Assigned To | => rafaroda |
| 2009-04-22 20:18 | psarobe | Tag Attached: Modularity | |
| 2009-04-22 20:18 | psarobe | OBNetwork customer | => No |
| 2009-04-22 20:18 | psarobe | Assigned To | rafaroda => alostale |
| 2009-04-22 20:18 | psarobe | Status | new => scheduled |
| 2009-04-23 12:25 | alostale | Regression testing | => No |
| 2009-04-23 12:25 | alostale | Relationship added | duplicate of 0007623 |
| 2009-04-23 12:25 | alostale | Status | scheduled => closed |
| 2009-04-23 12:25 | alostale | Duplicate ID | 0 => 7623 |
| 2009-04-23 12:25 | alostale | Resolution | open => duplicate |
| 2009-04-24 00:00 | anonymous | sf_bug_id | 0 => 2779922 |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |