Bug 143535

Summary:	Kexi does not import all field types correctly from MySQL tables. It assumes varchar is BLOB.
Product:	[Applications] KEXI	Reporter:	Edward <edwardiv1>
Component:	Migration/Import/Export	Assignee:	Kexi Bugs <kexi-bugs>
Status:	CONFIRMED ---
Severity:	normal
Priority:	NOR
Version:	1.1.2 (KOffice 1.6.2)
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Edward 2007-03-28 07:45:46 UTC

Version:           1.1.2 (KOffice 1.6.2) (using KDE 3.5.6 "release 19.1" , openSUSE )
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.18.8-0.1-default

When I import a table from MySQL and the destination is also a different database in MySQL, kexi creates the new tables with BLOB fields when they are in fact varchar fields in the original tables. Changing them to Text in kexi truncates the data. I had to manually hack the kexi__ tables to tell it they were text fields. This was important because I wanted to edit the text data in kexi, but if the field is BLOB, kexi thinks it is an image and gives me a drop-down box instead of a text edit box for that field.

I suggest some way to re-scan the source tables and update the kexi__ tables based on that, or do away with the kexi__ tables altogether and scan the source table structures on start-up.

The main good thing about kexi is what it treats views as tables, so it allows editing of views when the DB server (e.g. MySQL) supports it. Other programs (e.g. openoffice) assume that all views are read-only.

Comment 1 Jarosław Staniek 2007-03-28 10:00:30 UTC

Thanks for reporting. Assigned. 

Removed "Changing it after import truncates the table." from the titme because it is the (unexpected by many) behaviour related to Table Designer itself, not migration framework. A wish for it is reported here: http://bugs.kde.org/show_bug.cgi?id=125253

I have also written something about the feature here: http://www.kdedevelopers.org/node/2075

Regarding relying on server's introspecion capabilities for db schema, in Kexi 2.x there will be linking to external "native" tables/views (as in MS Access, but with more options for fine-tuning), and in general Kexi will trust more information fetched from server than from kexi__ tables (if possible).

Comment 2 Justin Zobel 2021-03-09 23:43:44 UTC

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.