Using a database for version history

Hi all,

I am working on a large project where we are replacing a CM system with Teamsite. As they use a version control tool at present they want the same info to come out of Teamsite. My solution to this is to use a database to store the extra info (too much for extended attributes really).

Does anyone have experience of this?

Does this fall into 'accepted practice'?

I think a lot of the requirement for the extra version info will disappear when they are familiar with the product but I need to help them in the initial stages.

Any comments would be greatly appreciated

John

Find more posts tagged with

Comments

Bowker

John,

This typically gets our business partners to re-evaluate their 'unusual' requests (like "I need this logging information")...

Ask them for documented specifics on why they need it and what is the Return On Investment.

If they give you a valid answer you'll need to do it. I would suggest looking at triggers (Command Line Tools to setup actions to occur on specific events)

Dan Bowker