On Oct 1, 2006, at 12:42 PM, Ilias Lazaridis wrote:
> > > Ilias Lazaridis wrote: >> Matt Good wrote: >>> Ilias Lazaridis wrote: >>>> Is there a standard way defined for adding fields to the datamodel? >>> >>> No, this is not currently supported, but there has been >>> discussion of >>> making the Trac object model more flexible. At this time if you >>> need >>> extra information you can use a separate table to store your data. >>> >>> The Tags plugin is one example of storing fields related to wiki >>> pages: >>> http://muness.textdriven.com/trac/wiki/tags/Setup >>> >>>> * how do I add a field in the existent table >>> >>> Don't. Field you add to Trac's built-in tables may be lost when >>> Trac >>> upgrades its schema. If you need additional fields they should be >>> stored in a separate table with a foreign-key style relation to the >>> Trac tables. >> >> I don't like tables and SQL, would like to avoid them. >> >> Thus it seems to be less effort to create a custom field and to >> handle >> the upgrade than to create foreign-key relations and new tables. >> >> Is there a possibility to get a customization field included in the >> core-version? > > ??? > >> I could workout a flexible solution (which I would use, but other >> could >> use it, too). >> >> -- >> http://lazaridis.com It is not likely that there will be a uniform way to do this for a while at least. Look at the TracObjects proposal (on trac.edgewall.org) for more info on one suggested method. Until then what Matt said is the best way to do it, secondary tables with change listeners to keep it all in sync. --Noah --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac 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/trac-users -~----------~----~----~----~------~----~------~--~---
