[squeak-dev] Re: Squeaksource data loss?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

[squeak-dev] Re: Squeaksource data loss?

Torsten Bergmann
>Unfortunately MCM files are not stored on the filesystem (support was added >later and does not cleanly integrate into the persistency system), and thus
>are not persistent after a crash.

Ohhh nice ... I once uploaded an MCM but was not able to delete it from
one of my projects since it was not deletable from the web interface.
Now the project is clean. Thanks for the crash ;)

Bye
Torsten

BTW: Is'nt there a regular backup of the machine or ZIP of the SqS folder?


--
Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3 -
sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser

Reply | Threaded
Open this post in threaded view
|

Re: [squeak-dev] Squeaksource data loss?

Lukas Renggli
> Ohhh nice ... I once uploaded an MCM but was not able to delete it from
> one of my projects since it was not deletable from the web interface.
> Now the project is clean. Thanks for the crash ;)

Yeah, that's because MCMs are not implementede polymorphic to MCZs.

> BTW: Is'nt there a regular backup of the machine or ZIP of the SqS folder?

Yes, but only MCZs that are persistent right after the commit. I don't
know why the MCM mechanism was implemented orthogonal?

Lukas
>
>
> --
> Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3 -
> sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser
>
>

--
Lukas Renggli
http://www.lukas-renggli.ch

Reply | Threaded
Open this post in threaded view
|

Re: [squeak-dev] Squeaksource data loss?

Igor Stasenko
2009/7/19 Lukas Renggli <[hidden email]>:

>> Ohhh nice ... I once uploaded an MCM but was not able to delete it from
>> one of my projects since it was not deletable from the web interface.
>> Now the project is clean. Thanks for the crash ;)
>
> Yeah, that's because MCMs are not implementede polymorphic to MCZs.
>
>> BTW: Is'nt there a regular backup of the machine or ZIP of the SqS folder?
>
> Yes, but only MCZs that are persistent right after the commit. I don't
> know why the MCM mechanism was implemented orthogonal?
>
sounds like a new task for MC maintainers/devs :)

> Lukas
>>
>>
>> --
>> Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3 -
>> sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser
>>
>>
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
>
>



--
Best regards,
Igor Stasenko AKA sig.

Reply | Threaded
Open this post in threaded view
|

Re: [squeak-dev] Squeaksource data loss?

Bert Freudenberg
On 19.07.2009, at 01:53, Igor Stasenko wrote:

> 2009/7/19 Lukas Renggli <[hidden email]>:
>>> Ohhh nice ... I once uploaded an MCM but was not able to delete it  
>>> from
>>> one of my projects since it was not deletable from the web  
>>> interface.
>>> Now the project is clean. Thanks for the crash ;)
>>
>> Yeah, that's because MCMs are not implementede polymorphic to MCZs.
>>
>>> BTW: Is'nt there a regular backup of the machine or ZIP of the SqS  
>>> folder?
>>
>> Yes, but only MCZs that are persistent right after the commit. I  
>> don't
>> know why the MCM mechanism was implemented orthogonal?
>>
> sounds like a new task for MC maintainers/devs :)


No, for SqueakSource server developers.

At the time I added the MCM support, it was saved just like the rest  
of the meta data. MCZs were saved to disk immediately but became  
inaccessible on a crash. So there was not much incentive to do better  
than that.

- Bert -