Publishing an EDITION and disk space growth

Hi,

I tried to RTFM, but didn't find it . . .in the TeamSite 6.x suite, is creating a new EDITION still "lean" in the sense that you don't actually get a physical copy of every file in your STAGING area?

I remember that's the way it worked back in the old 5.x days, but just wanted to confirm...

TIA,
Tom

Find more posts tagged with

Comments

Frederik

Correct.

Publishing an edition is the act of giving a name to an unnamed edition. Unnamed editions (which have a name like "#123") are created at every submit action. They *logically* refer to all the files in STAGING at that time.

PS: I could have stopped at "Correct" but the forum software demands more than 10 chars in a response :cool:

Adam Stoller

Hi,

I tried to RTFM, but didn't find it . . .in the TeamSite 6.x suite, is creating a new EDITION still "lean" in the sense that you don't actually get a physical copy of every file in your STAGING area?

I remember that's the way it worked back in the old 5.x days, but just wanted to confirm...

TIA,
Tom

To the best of my knowledge this has never changed and is probably unlikely to ever do so.

Migrateduser

Every asset (file, dir, hole..) has the only one version stored in the backing store as far it is logically same. Thus a file in the STAGING,EDTITION, UPDATED WORKAREA has only one storage entity in the backing store.
If some one changes the workarea file, newer version of it is created, but the STAGING and EDITION still have a single older file pointed. Submitting new file from workarea makes the STAGING also to refer to this new version (still EDITION is pointing to OLD) and if publishing the new EDITION the newer version is pointed by EDITION also accordingly.