ofbiz-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suraj Khurana (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OFBIZ-10921) Marital Status not managed properly in Person entity
Date Fri, 26 Apr 2019 12:09:00 GMT

    [ https://issues.apache.org/jira/browse/OFBIZ-10921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826918#comment-16826918
] 

Suraj Khurana commented on OFBIZ-10921:
---------------------------------------

Thanks everyone for your inputs,

I have attached patch with only two enums as of now, Single and Married.

Also, here is the alter query: 
{code:java}
alter table person change MARITAL_STATUS MARITAL_STATUS VARCHAR(20);{code}

> Marital Status not managed properly in Person entity
> ----------------------------------------------------
>
>                 Key: OFBIZ-10921
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-10921
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: party
>    Affects Versions: Trunk
>            Reporter: Suraj Khurana
>            Assignee: Suraj Khurana
>            Priority: Major
>         Attachments: OFBIZ-10921.patch
>
>
> Currently, *maritalStatus* is managed as an indicator (Y/N) in *Person*
>  entity. I think we can enhance it and make it derived from *Enumeration*
>  pattern.
>  
>  *Classification of legal marital status*
>  
>     - 1 - Married (and not separated) ...
>     - 2 - Widowed (including living common law) ...
>     - 3 - Separated (and not Divorced) ...
>     - 4 - Divorced (including living common law) ...
>     - 5 - Single (including living common law)
> Please refer discussion over ML:
> [https://markmail.org/message/5b33qm3osy76if24]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message