no it will not erase it, as the upgrade just added a custom field to
your database. it is stored in the ticket_custom table, id is filled
with the ticket number, and name is name is the name of the custom
field. a trac upgrade does not touch these custom fields.

oyu might also install the custom fields plugin to see it in the
admin.

see here an example of a report selecting custom field "progress":

SELECT p.value AS __color__,
   milestone||' Release' AS __group__,
   id AS ticket, summary, component, version, t.type AS type,
   owner, status,
   time AS created,
   changetime AS _changetime, description AS _description,
   reporter AS _reporter,
   tc.value AS progress
  FROM ticket t
  LEFT JOIN enum p ON p.name = t.priority AND p.type = 'priority'
  LEFT OUTER JOIN ticket_custom tc ON (t.id=tc.ticket AND
tc.name='progress')


rupert.


On Jan 15, 12:05 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> I'm running 0.11b1 Trac release and I found an interesting 
> pluginMasterTicketsPluginand installed 
> ithttp://trac-hacks.org/wiki/MasterTicketsPlugin
> This plugin ask me to trac-admin env upgrade my trac environment. I
> did it and restarted Apache/mod_python. The plugin works fine now but
> I'm pretty sure that it has updated the DB schema.
>
> My question : My users will use this functionality and will fill the
> database. What will happen when I upgrade my trac code ? Upgrade guide
> says that trac code has to be updated and then a trac-admin env
> upgrade has to be run...
>
> I wonder if this trac-admin env upgrade will erase all the stuff
> generated by the plugin extension...
>
> Any explanations for a newbie ?
>
> Thanks !
>
> pierre
--~--~---------~--~----~------------~-------~--~----~
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?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to