On Jun 27, 2009, at 9:57 PM, Harmeet Bedi wrote:
Regd: 'Doing an automated migration would only work if you know that
all
current values in the database are among the enumerated options you
want to
migrate to'
Migration could check and create the enumerated option if it does
not exist.
How would this be better than the current practices? These are
described here:
http://docs.ofbiz.org/display/OFBTECH/Revisions+Requiring+Data+Migration
and here:
http://docs.ofbiz.org/display/OFBTECH/General+Entity+Overview ->
Deprecated Entities
-David
On Jun 27, 2009, at 10:58 PM, H
How about this proposal
1. Add enumeration id in addition to text field for these and any other
places where text could be replaced with reference. Some locations
(a) add Person::salutationTypeId references
PersonSalutionType:salutationTypeId
(b) add Person:personalTitleTypeId references
Person
Regd: 'Doing an automated migration would only work if you know that all
current values in the database are among the enumerated options you want to
migrate to'
Migration could check and create the enumerated option if it does not exist.
So Party has refrences to PersonalTitleId, where PersonalT
Yeah, that's the exact issue with the title too... there are
potentially thousands of them if you try to include every culture in
the world (and hundreds even for English speaking cultures, especially
if you include royalty/class titles, military titles, etc). On the
other hand, now that
I would say yes - but it does limit us to what we know about - but
that's the case with any lookup.
Cheers,
Tim
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com
o:801.649.6594
f:801.649.6595
On Jun 27, 2009, at 11:32 AM, David E Jones wrote:
On Jun 27, 2009, at 8:07 AM, Jacopo Cappel
On Jun 27, 2009, at 8:07 AM, Jacopo Cappellato wrote:
On a side note, would you want to do this with the suffix or any
other fields?
I am sorry but I don't understand the above question.
The questions was mainly for Bob, but I guess something for anyone to
consider: would we want to ha
Hi David,
On Jun 27, 2009, at 1:42 AM, David E Jones wrote:
This is a tough one since you would be moving from a less
constrained field to a more constrained one, ie a free-form field to
a field with an enumerated set of options. Doing an automated
migration would only work if you know t
This is a tough one since you would be moving from a less constrained
field to a more constrained one, ie a free-form field to a field with
an enumerated set of options. Doing an automated migration would only
work if you know that all current values in the database are among the
enumerat
Hi Bob,
I agree that adding the new personalTitleEnumId is a good idea.
See also my comments inline:
On Jun 26, 2009, at 5:04 PM, Bob Morley wrote:
Bob Morley wrote:
We had a requirement to add some additional values to the personal
title
dropdown and noticed that the list of Personal Tit
Yes I am going to quote myself! LOL
I was hoping to get some input on this specifically in the area of the
migration concerns. In our application we have converted the personal title
drop-down to an enumeration, but I still store the localized personal title
value. We will definitely want to s
We had a requirement to add some additional values to the personal title
dropdown and noticed that the list of Personal Titles were hardcoded in the
application. Once more, they were stored with the localized value in the
database. It seemed that the correct thing to do would be to introduce an
12 matches
Mail list logo
