Kexi/Stability Statement: Difference between revisions
m (Jstaniek moved page Kexi/Kexi Stability Statement to Kexi/Stability Statement) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
=== Application Stability === | |||
It is recommended to back up your data when you're working with beta versions of any software. However, even KEXI beta versions are relatively stable. If you're wondering about possibility of data loss, note that any data-related operations are protected by [https://en.wikipedia.org/wiki/Database_transaction database transactions]. | |||
=== Unstable features === | |||
Unstable features are marked as experimental. They are not enabled by default and thus cannot be used unless a special (development) version of KEXI is installed. | |||
=== Compatibility between KEXI versions === | |||
Regarding to format stability, there is a policy of [http://en.wikipedia.org/wiki/Backward_compatibility backward compatibility]. In most cases there is also support for [http://en.wikipedia.org/wiki/Forward_compatibility forward compatibility]. This is possible because definitions for stored objects contain version information and KEXI takes care about differences between format versions. | |||
=== Compatibility between KEXI and external formats === | |||
When possible, importing, exporting and data exchange is performed using well known and widely available software tools. For example, MS Access database format is handled through the [http://mdbtools.sourceforge.net/ mdbtools] library. | |||
Latest revision as of 23:52, 15 October 2024
Application Stability
It is recommended to back up your data when you're working with beta versions of any software. However, even KEXI beta versions are relatively stable. If you're wondering about possibility of data loss, note that any data-related operations are protected by database transactions.
Unstable features
Unstable features are marked as experimental. They are not enabled by default and thus cannot be used unless a special (development) version of KEXI is installed.
Compatibility between KEXI versions
Regarding to format stability, there is a policy of backward compatibility. In most cases there is also support for forward compatibility. This is possible because definitions for stored objects contain version information and KEXI takes care about differences between format versions.
Compatibility between KEXI and external formats
When possible, importing, exporting and data exchange is performed using well known and widely available software tools. For example, MS Access database format is handled through the mdbtools library.