| Register | FAQ | Calendar | Search | Today's Posts | Mark Forums Read |
|
#1
| |||
| |||
| Hi all, how to remove the repository funcionality or how to reduce it (I´ve got a 200MB repository). Thanks a lot Cheers Marco |
|
#2
| |||
| |||
| Marco, > how to remove the repository funcionality or how to reduce it (I´ve > got a 200MB repository). I'm doing an automatic backup/reorganize(garbage collect) as part of my image startup script (http://readthesourceluke.blogspot.co...up-script.html). The following might help: "Connect STS Repositry" stsRepositryPath := 'S:\Dolphin Smalltalk X6\STS Repositry'. StsManager startUpOn: stsRepositryPath. "Backup Repositry and reorganize" stsBackupPathStream := ReadWriteStream on: String new. stsBackupPathStream nextPutAll: stsRepositryPath; nextPutAll: '/Repository.BACKUP_'. Date today printOn: stsBackupPathStream format: 'yyyyMMdd'. Time now printOn: stsBackupPathStream format: 'HHmmss'. (StsManager current databaseConnection) createBackupOn: stsBackupPathStream contents; reorganize. CU, Udo |
|
#3
| |||
| |||
| On Jul 28, 5:57*pm, Udo Schneider <Udo.Schnei...@homeaddress.de> wrote: > Marco, > > > how to remove the repository funcionality or how to reduce it (I´ve > > got a 200MB repository). > > I'm doing an automatic backup/reorganize(garbage collect) as part of my > image startup script > (http://readthesourceluke.blogspot.co...startup-script...). > > The following might help: > > "Connect STS Repositry" > stsRepositryPath := 'S:\Dolphin Smalltalk X6\STS Repositry'. > StsManager startUpOn: stsRepositryPath. > "Backup Repositry and reorganize" > stsBackupPathStream := ReadWriteStream > * * * * * * *on: String new. > stsBackupPathStream > * * *nextPutAll: stsRepositryPath; > * * *nextPutAll: '/Repository.BACKUP_'. > Date today > * * *printOn: stsBackupPathStream > * * *format: 'yyyyMMdd'. > Time now > * * *printOn: stsBackupPathStream > * * *format: 'HHmmss'. > (StsManager current databaseConnection) > * * *createBackupOn: stsBackupPathStream contents; > * * *reorganize. > > CU, > > Udo Hi Udo, thanks for your answer. But how to remove the repository? What, if I would like to work without the repository from now on? Is that possible? Thanks Marco |
|
#4
| |||
| |||
| Marco, > But how to remove the repository? What, if I would like to work > without the repository from now on? Is that possible? As long as you don't use any STS functions you can simply delete it. You may have to reset StsMananger into a state where it doesn't know about the repository to prevent file lock errors on the OmniBase DB. "StsManager current shutdown" should do the trick. After this you can delete the Repository. However I'm not sure whether you can simply uninstall the STS package completly. It's not that I know of any issues - it's just that I never tried it. CU, Udo |
|
#5
| |||
| |||
| Marco, > However I'm not sure whether you can simply uninstall the STS package > completly. It's not that I know of any issues - it's just that I never > tried it. Just one more thing as I cannot believe someone wants to work with STS: If you versioned all the standard image packages into STS this might be the reason why the repository is so big. If you limit yourself to versioning only your own packages and do a reorganize once in a while the repository size normally remains a lot smaller. CU, Udo |
|
#6
| |||
| |||
| > Just one more thing as I cannot believe someone wants to work with STS: This should have been "[...] work withOUT STS [...]" of course. Sorry David :-) CU, Udo |
|
#7
| |||
| |||
| Udo Schneider wrote: > > However I'm not sure whether you can simply uninstall the STS package > completly. It's not that I know of any issues - it's just that I never > tried it. > > CU, > > Udo You can uninstall STS like any other package. But you should not do this while the database is still open. Evaluate "StsManager shutdown" before uninstalling the package. |
![]() |
| Thread Tools | |
| Display Modes | |
In an effort to better serve ads to our visitors, cookies are used on objectmix.com. For more information, check out our Privacy Policy.