Kexi/Compatibility: Difference between revisions

From KDE Community Wiki
(update)
Line 3: Line 3:
{{Note|Should you notice any misfeature or incompatibility not listed here feel free to [[../Contact/|contact us]].}}
{{Note|Should you notice any misfeature or incompatibility not listed here feel free to [[../Contact/|contact us]].}}


== Compatibility with KEXI 2 ==
'''KEXI 2 -> KEXI 3'''. KEXI 3 offers the same list of features as KEXI 2 and uses the same format for <tt>.kexi</tt> files and supports server projects (MySQL, PostgreSQL) with the following exceptions:
Status for KEXI 3.0 and 3.1. KEXI offers the same list of features as KEXI 2 and uses the same format for <tt>.kexi</tt> files and server projects (MySQL, PostgreSQL).
* No scripting. In KEXI 2 scripting was offered as experimental. We plan to deliver brand new Python based scripting in the future.
Exceptions (status for 3.1):
* No "map" report elements. Supported again since KEXI 3.2. Some behaviors may be different due to a new version of the map component.
* no scripting (in KEXI 2 it was present as experimental), we plan to deliver brand new JavaScript support (without web browser overhead)
* No "map" form widgets.
* "map" report elements: not supported until KEXI 3.1
* "map" form widgets: not supported


'''KEXI 1 -> KEXI 3'''. Support for server projects other than MySQL and PostgreSQL are discontinued. In KEXI 1 there were more servers supported (albeit marked as experimental). KEXI 1 used SQLite backend version 2 while KEXI 2 moved to SQLite version 3, incompatible with version 2. Migration tools to the new version have been released.


Further KEXI version would, of course, get new features not present in KEXI 2.
'''KEXI 1 -> KEXI 2.2.''' Please refer to the list here [https://community.kde.org/Kexi/Releases/Kexi_2.2#Missing_or_discontinued_features_in_2.2].


Like most older KEXI version, KEXI 3 has no official support for server projects other than MySQL and PostgreSQL.
'''KEXI 1 vs commercialy supported versions'''. KEXI 1 was also available as commercially supported versions such as "Kexi 2007". These versions offered potential differences however used the same file format.
 
== Compatibility with KEXI 1 ==
 
KEXI 1 was also available as commercially supported versions such as "Kexi 2007". These versions offered potential differences however used the same file format.
 
'''KEXI 2.2 - KEXI 1.''' Please refer to the list here [https://community.kde.org/Kexi/Releases/Kexi_2.2#Missing_or_discontinued_features_in_2.2].

Revision as of 12:49, 17 May 2023

This page documents current status for compatibility of KEXI 3 with earlier versions of KEXI.

Note

Should you notice any misfeature or incompatibility not listed here feel free to contact us.


KEXI 2 -> KEXI 3. KEXI 3 offers the same list of features as KEXI 2 and uses the same format for .kexi files and supports server projects (MySQL, PostgreSQL) with the following exceptions:

  • No scripting. In KEXI 2 scripting was offered as experimental. We plan to deliver brand new Python based scripting in the future.
  • No "map" report elements. Supported again since KEXI 3.2. Some behaviors may be different due to a new version of the map component.
  • No "map" form widgets.

KEXI 1 -> KEXI 3. Support for server projects other than MySQL and PostgreSQL are discontinued. In KEXI 1 there were more servers supported (albeit marked as experimental). KEXI 1 used SQLite backend version 2 while KEXI 2 moved to SQLite version 3, incompatible with version 2. Migration tools to the new version have been released.

KEXI 1 -> KEXI 2.2. Please refer to the list here [1].

KEXI 1 vs commercialy supported versions. KEXI 1 was also available as commercially supported versions such as "Kexi 2007". These versions offered potential differences however used the same file format.