The Latest Word Marketing HelixChat Contact Us Policies 3rd Party

Reviews Testimonials Field Reports Museum Who Uses Helix Surveys

When we did the OS X Helix Server (Helix Server 6.0) we chose to make the Save and Log feature transparent. This was done primarily because of reports of data loss in Helix Server when somebody inadvertently turned logging off. This typically happened when a collection was taken into Design Mode in RADE for structural changes, but it could also occur by other means. Beginning in Helix 6.0, transaction logging is turned on automatically each time the collection is opened.

Since automatic transaction logging is now the default situation (but was never a feature of a Helix product before) we wanted to solicit your input on whether it should remain that way in Helix Engine. We would like to leave it this way for three reasons:

1. The notion of data safety — that your data is preserved in the case of a crash — is important to us.
2. We would like to make this feature transparent for novice users who may not care to learn the details about transaction logging.
3. Leaving it on saves us a little time in not having to revise that code.

For users who do not want transaction logging on, there are currently two options:

1. The Transaction Logging Preference is available for disabling logging by default.
2. The Save and Log… menu command is fully functional, so you can choose Save and Stop Logging when the collection is open to disable logging (and re-enable it) as you prefer.

This survey ran May 22 – July 5, 2007.

147 users responded to this survey.

Since the overwhelming majority of you are comfortable with having transaction logging automatically turned on, we will not revise the code. Those who want to turn it off can use the preference to disable the feature.