I'd recommend subclassing Category and create your own custom CustomCategory class. You will have minimal impact on Satchmo operations, will ensure that a Satchmo category is saved/updated each time a CustomCategory is saved/updated, and will have a model that you can define any methods you need for without affecting Satchmo and breaking your upgrade path.
On Wed, Mar 18, 2009 at 3:07 AM, welyou <[email protected]> wrote: > > We develop http://code.google.com/p/django-satchmo-tuning/ " - "Tuning > Satchmo for wholesale store" > > We tuning Satchmo for web presentation of data stored in accounting > system. > > And have problem, how to correct extend Category (subclass/inherit or > create one-to-one relation with addition entity)? > > Every hour data from account system will be uploaded/updated into site > shop data base. > > In accounting system category have code and name attributes, for > ability sync operation between site and accounting system i must have > "code". > > Addition "active" attribute we needed for hide some category from > category catalog. > > How do this more correct? > > Help, please :)! > > P.S. > Maybe Satchmo developers add "code,active" into class Category source > satchmo? > > Needing of "active" attribute for Category already discussed. > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en -~----------~----~----~----~------~----~------~--~---
