[
https://issues.apache.org/jira/browse/OFBIZ-13329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18055955#comment-18055955
]
Jacques Le Roux commented on OFBIZ-13329:
-----------------------------------------
Hi Nicolas,
Not sure it's related but I found this in trunk demo error.log today:
2026-02-02 02:36:51,801 |OFBiz-batch-2 |DatabaseUtil
|E| [marital_satus_enum_id] to table [public.PERSON]: SQL Exception
while executing the following:
ALTER TABLE public.PERSON ADD marital_satus_enum_id VARCHAR(20)
Error was: org.postgresql.util.PSQLException: ERROR: column
"marital_satus_enum_id" of relation "person" already exists
> Manage marital status type history for person
> ---------------------------------------------
>
> Key: OFBIZ-13329
> URL: https://issues.apache.org/jira/browse/OFBIZ-13329
> Project: OFBiz
> Issue Type: Improvement
> Components: party
> Reporter: Nicolas Malin
> Assignee: Nicolas Malin
> Priority: Minor
> Labels: history, marital, person
> Attachments: OFBIZ-13329.patch
>
>
> Currently, on the framework we can add a marital status to a person through
> enumeration on entity Person.
> But we can't manage the history of change. After scan the data model book, we
> proposed to improve party model entity with two new entities :
> * MaritalStatus : to stock the history of marital status change
> * MaritalStatusType : like Len Silverton suggest on his book to isolate
> these types.
> We move the current field *maritalStatusEnumId* to deprecated and introduce a
> migration service to move field *maritalStatusEnumId* to *maritalStatusTypeId*
>
> Thanks to Charles Steltzlen for this improvement
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
