Opened 12 years ago
Closed 12 years ago
#1731 closed defect (fixed)
Update fails if an item subtype with the same name as a new system-defined subtype has already been manually registered
| Reported by: | Nicklas Nordborg | Owned by: | Nicklas Nordborg |
|---|---|---|---|
| Priority: | critical | Milestone: | BASE 3.2.1 |
| Component: | install | Version: | 3.2 |
| Keywords: | Cc: |
Description
As an example, BASE 3.2 add a 'Cabinet' subtype. If a subtype with this name has already been manually added on an existing BASE server the update fails with a database error about 'duplicate entry for key...'. Eg. it tries to insert another subtype with the same name as the one that already exists.
The bad thing about this error is that it leaves the BASE installation in an unusable state. It is not possible to start the BASE server and fix this (by renaming the subtype) via the web interface.
A possible workaround is to manually execute an SQL statement that changes the name of the existing subtype. Something like this (replace 'foo' with the actual name):
update ItemSubtypes set name=name+'.old' where name='foo'
The other alternative is to revert to the previous BASE version by restoring from a backup.
Change History (2)
comment:1 by , 12 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
(In [6152]) Fixes #1731: Update fails if an item subtype with the same name as a new system-defined subtype has already been manually registered