Non-Unique model names on migrating AC3.6 to AC4.2

[traceyr]

Hi!

Our 3.6 DB contains products with non-unique model names, e.g. (fictitious) Brand=IBM Model=3400 and Brand=HP Model=3400, in the same category.

In 4.2 there is a uniqueness constraint on a Model's name/full name, leading to a DB error (on full name).:

2003/05/23 10:06:42.405 3 1 (-2004) Oracle error: 'ORA-00001:
unique constraint (MODEL_FULLNAME) violated'
2003/05/23 10:06:42.405 3 1 (-2004) Oracle error: 'ORA-06512: at
line 2'
2003/05/23 10:06:42.395 3 1 (-2004) Index error: A record in
table 'Models (amModel)' with the value '/personal computer/desktop
computer/optiplex gx150/' for field 'Full name (FullName)' already exists in
the database.
2003/05/23 10:06:42.375 1 1 (-2004) Unable to create 'optiplex
gx150' in table 'Models (amModel)'.

Peregrine have suggested inserting the 'brand' as a node in the model hierarchy ...

Thanks in advance for any ideas.

 

[pearljam]

Yes: there is a unicity constarint on model's fullname.
Yes: using the brand is the best.