Bug 307571 - MySQL-syntax-error on database-import
Summary: MySQL-syntax-error on database-import
Status: CONFIRMED
Alias: None
Product: KEXI
Classification: Applications
Component: Migration/Import/Export (show other bugs)
Version: 2.5.2
Platform: openSUSE Linux
: NOR major
Target Milestone: ---
Assignee: Kexi Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-29 11:39 UTC by Guido Schmidt
Modified: 2021-03-09 23:43 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Database-structure exported with phpMyAdmin (2.15 KB, application/x-bzip)
2012-09-29 11:43 UTC, Guido Schmidt
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Guido Schmidt 2012-09-29 11:39:32 UTC
I have a MySQL-db with foreign key constraints. When I try to import it's structure into another MySQL-db I get an MySQL-syntax-error.

Reproducible: Always

Steps to Reproduce:
1. Select the source-location and db
2. Select the destination-type, title, project filename and db
3. Set type of import to "Structure only"
4. Help the importer by selecting the data type for a field (in this case Serviceposition.KVA which is decimal(7,2))
Actual Results:  
Failure
Import failed
Could not import data from data source ...
Not connected to the database server.
Message from server: You have an error in your SQL syntax; [...] near 'UNSIGNED NOT NULL, `status` VARCHAR(255) NOT NULL' at line 1
Server result: 1064

Expected Results:  
Imported db.
(BTW: It would be nice if it were possible to mark the message window text for copying it)

This is the db I was refering to in Bug #307479. I'm going to attach it here.
Comment 1 Guido Schmidt 2012-09-29 11:43:21 UTC
Created attachment 74229 [details]
Database-structure exported with phpMyAdmin
Comment 2 Jarosław Staniek 2012-10-01 22:17:31 UTC
Thanks for the valuable report, I'll investigate it as soon as possible.
Comment 3 Justin Zobel 2021-03-09 23:43:33 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.