You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Jacques Le Roux (JIRA)" <ji...@apache.org> on 2006/07/08 10:10:30 UTC

[jira] Commenté: (OFBIZ-81) Support for PaymentMethod.description

    [ http://issues.apache.org/jira/browse/OFBIZ-81?page=comments#action_12419847 ] 

Jacques Le Roux commented on OFBIZ-81:
--------------------------------------

Hi Chris, David,

I'm very far to be a DB specialist (actually I always tried to avoid working with DB, my background is IA, symbolic-logical part) but I find this discusssion interesting. 

The main reason is that I worked at the beginning in OFBiz mostly on i18n. And I had a hard time understanding the way OFBiz manages description (aka content).

I think that Chris as a point when he say :

<<Catalog Manager -> Product -> Content -> Override Simple Fields screen would update the ElectronicText Entity, and then a SECA or ECA would update the Product Entity's redundant, denormalized field. In other words, the data in Product.longDescription would exist in the ElectronicText? entity. If it were redundant, you could still find all of the Product Content in a single entity. Because there is only _apparent_ redundancy, you need to look in two places to obtain a complete set of a product's content. 

The current pattern is trying to obtain the benefits of redundancy in querry at the cost of finding information where it is expected to be found. It's not necessary. If you want the benefit of redundancy in query then actually be redundant.>>

I can't say more for the moment, I agree with Chris about this point but have not enough time yet to think about a solution around description/content and i18n problem.  What is interesting me at most is to build an *easier* interface for admin to modify i18n contents (name, descriptions) of at least catalogs, categories and products (did I miss something here?).

About that point I propose a patch in OFBIZ-75 for i18n of categories. If a commiter has some time to spent...

Thanks

Jacques

> Support for PaymentMethod.description
> -------------------------------------
>
>          Key: OFBIZ-81
>          URL: http://issues.apache.org/jira/browse/OFBIZ-81
>      Project: The Open For Business Project
>         Type: New Feature

>   Components: accounting
>     Reporter: Si Chen
>     Priority: Minor

>
> Add additional field "description" to PaymentMethod to describe the payment method (ie, "Joe's credit card" or "Our main checking account")
> Add support for this field in the create, update, and view payment method services.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira