On Tue, Feb 9, 2010 at 1:37 PM, Noah Kantrowitz <[email protected]> wrote:
> > On Feb 8, 2010, at 9:43 PM, Vishal wrote: > > Hi, >> >> I would like to add some extra data to the trac installation I have, >> and for this I may need to add extra tables to the database being >> used. Since the database schema will change from the default one, i >> would like to know under what situations will a trac database update >> be required (as done by using the upgrade command from trad-admin)? >> Also, if there is no way to avoid the upgrade, is there a way to do >> this seamlessly, so a user does not know about it. >> >> > My snippet for doing this is > http://trac-hacks.org/browser/tracforgeplugin/0.11/tracforge/admin/api.py#L69 > > > http://trac-hacks.org/browser/tracforgeplugin/0.11/tracforge/admin/db_default.py > shows > how I setup my schema. > > As for making it transparent, no, Trac doesn't work that way. This is > primarily for safety reasons. DDL changes (like changing tables) generally > can't be rolled back as part of a transaction if the upgrade fails, so you > could end up with a bad DB. This is why trac-admin upgrade makes a backup > for you if possible (or requires you to state that you are okay without one > since you took a DB backup yourself). > > > An example for this situation is the client plugin. Whenever I try to >> add a new client or change anything in the client custom filed, the >> trac project asks me to do an upgrade. This would be sort of very >> difficult for the end user, particularly since they wont have admin >> permissions, but would need to to add a client nonetheless. >> >> > I don't know what the client plugin is doing, but changing custom fields > doesn't require a DB change, it doesn't even require a server restart. > > > --Noah > Yes I agree that custom tickets and their options etc, donot even require a server restart. Actually here is the issue, I would like add some custom ticket entries of 'select' type. The options in this case could well be in hundreds. I was thinking, if it would be possible to store these in the db, instead of the INI. I am in the process of creating a customer database to be used with the issue tracking done in TRAC, and we would like to create a release management system as well. Do bring realease management, customer management and issue management into a customized whole, it seems proper that we might have to add new tables to the db. If the upgrade is unavoidable, it would mean, we'll have to make sure the admin adds new stuff to these tables. Guess I am unclear about how one can write to new tables and avoid upgrades. Is that possible? Thanks and best regards, Vishal -- Thanks and best regards, Vishal Sapre --- "So say...Day by day, in every way, I am getting better, better and better !!!" "A Strong and Positive attitude creates more miracles than anything else. Because...Life is 10% how you make it, and 90% how you take it" "Diamond is another piece of coal that did well under pressure” "May we do good and not evil. May we find forgiveness for ourself and forgive others. May we share freely, never taking more than we give." -- 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.
