Bug 121933

Summary:	Errors in Kexi package (KOffice Database)
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Jarosław Staniek <js>
Component:	KDE	Assignee:	E-mail List <kde-maintainers>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P3 - Medium
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:
Found By:	Development	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Jarosław Staniek 2005-10-10 10:35:07 UTC

Kexi has bundled its own version of SQLite 2 and 3. I can see you removed it and
added a dependency on reguilar sqlite package. This will cause crashes and/or
nonworking Kexi features, like sqlite2->sqlite3 conversions. Compatibility with
sqlite2 is thus broken.

Decision for bundling sqlite with Kexi has been made because of a need for 
long-term compatibility.

Proposed solution: 
1. revert "external-sqlite.diff" patch
2. in the future: ask Kexi maintainer before such internal change is performed

Comment 1 Jarosław Staniek 2005-10-10 10:43:07 UTC

More info: 
- Source package: koffice 1.4.1
- bug report originally published here:
http://www.kexi-project.org/wiki/wikiview/index.php?KnownErrorsInKexiPackages#SuSE_Linux_10.x

Comment 2 Jarosław Staniek 2005-10-10 10:51:09 UTC

Other errors:
- no ksqlite and ksqlite2 (because of the absence of kexisqlite*)
- PostgreSQL, MySQL driver bundled with KOffice, making it hard to instal

Summing up, following report is also valid for SuSE 9.3...10.x:
http://www.kexi-project.org/wiki/wikiview/index.php?KnownErrorsInKexiPackages#SuSE_Linux_9.3

Comment 3 Stephan Binner 2005-12-16 15:22:49 UTC

How does the included SQlite 2 and 3 versions differ from the original? What patches? Why are they not mergeable or merged upstream?

Comment 4 Jarosław Staniek 2005-12-16 16:19:55 UTC

(In reply to comment #3)
> How does the included SQlite 2 and 3 versions differ from the original? What
> patches? Why are they not mergeable or merged upstream?
 
For now, data processing progress information (in text format) is sent to stdout. Kexi, as GUI app, depends on this, while original sqlite package is considered by authors as minimalitic (what's good). Many extensions like custom collation or behavioral tweaks in sqlite are performed by recompiling the source code. SQLite is just designed as a small piece of code (often used as static lib) embeddedable in other code.

So we want and need to embed sqlite in KexiDB, as sane default. 

Here's a patch for sqlite2 if you need e.g. to keep it in Kexi rpm:

http://websvn.kde.org/trunk/koffice/kexi/3rdparty/kexisql/src/patches/

Changes to SQLite3 are in progress, but for now - even outside of SVN, due to more important tasks.

Comment 5 Jarosław Staniek 2005-12-16 16:43:37 UTC

Stephan,

BTW, every .1 release of SQLite differs regarding to the way of a feature set and forward compatibility is not kept. 
E.g. Editing database using 3.1 breaks compatibility with 3.0.
Thus I need to know exactly what .1 version (3.0 or 3.1 in case od "3" series) I am working with to be able to protect users from silently messing up their data.

On SUSE side, for example: sqlite-3.1.3-3.i586.rpm package contains libsqlite3.so.0 and not libsqlite.so.0.8.6 so I can see no distiction between 3.0 and 3.1 version.

Having libsqlite3-1.so.0 or moving to libsqlite3.so.1 could help... but I know this probably will break existing SUSE installations. 

I am curious what can you see as a solution here.

Comment 6 Stephan Binner 2006-01-09 16:20:55 UTC

After discussion we decided to remove the patch (for 10.1).

Comment 7 Jarosław Staniek 2006-01-09 18:33:33 UTC

This means: SQLite2 projects are still not handled under SUSE.

FYI: Forthcoming KOffice 1.5 release (Kexi 1.0) contains more complex patch for SQLite3.