[
https://issues.apache.org/jira/browse/OFBIZ-9351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16115367#comment-16115367 ]
Aditya Sharma commented on OFBIZ-9351:
--------------------------------------
It won't be affecting that as these field types were only implemented at the code level & had no special significance at the database level i.e. both "id" and "id-ne" were same for the database.
> Remove unnecessary field types
> ------------------------------
>
> Key: OFBIZ-9351
> URL:
https://issues.apache.org/jira/browse/OFBIZ-9351> Project: OFBiz
> Issue Type: Improvement
> Affects Versions: Trunk
> Reporter: Aditya Sharma
> Assignee: Deepak Dixit
> Priority: Trivial
> Fix For: Upcoming Release
>
> Attachments: OFBIZ-9351.patch, OFBIZ-9351.patch, OFBIZ-9351_plugins.patch
>
>
> As discussed in
http://markmail.org/message/d2tpovewhtotukwa the "not empty" field types ("id-ne", "id-long-ne" and "id-vlong-ne") were initially added to implement validations on data. But, because the validations where only implemented in some place like webtools, it contradicts the distinction to be upheld on various layers. So it is better to remove these field types. So we will remove all those field types and will create sub tickets to replace them in entity definitions by corresponding "id" types.
> When replacing the "not empty" field types in entity definitions by corresponding "id" types we will add a *not-null="true"* attribute to "makes the field NOT NULL on the database (like primary key fields)" as explained in "not-null" documentation in fieldtypemodel.xsd. We will finally clean the documentation of the "not-null" in fieldtypemodel.xsd.
> Related Links:
>
http://ofbiz.135035.n4.nabble.com/EntityEngine-field-types-td2251546.html>
http://markmail.org/message/otec62xiwkpjttkq> A more vivid description:
>
http://ofbiz.markmail.org/thread/c6ee3ewyo6jpik7k--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
Locked
