MySQL Bugs: #32090: Data Mapping Options :: remove trailing spaces [data transfer error]

Bug #32090	Data Mapping Options :: remove trailing spaces [data transfer error]
Submitted:	4 Nov 2007 19:56	Modified:	17 Feb 2008 16:23
Reporter:	Eval User	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Migration Toolkit	Severity:	S3 (Non-critical)
Version:	1.1.12.0	OS:	Windows (XP Pro SP2)
Assigned to:		CPU Architecture:	Any
Tags:	Addendum to post [5 Nov 16:56] Eval User

Description:
Data Mapping Options [advanced (button)]
Checkbox: remove trailing spaces [enabled]

Causes error during insert script generation and/or data bulk transfer operations.

[Error log]

ERROR: The following error occured while transfering data from Clients
null

How to repeat:
Enable 'Data Mapping Options > remove trailing spaces'

Thank you for a problem report. Please, provide some more details about the schema and RDBMS you are migrating from. I was not able to repeat the behaviour described when I tried to migrate Oracle's SCOTT/TIGER demo schema to MySQL 5.0.x, for example.

Per Valeriy Kravchuk's request for additional details:

1. Origin RDBMS: MS-SQL Server 2005 Enterprise 'Evaluation' (recent download  and installation)

2. Destination: MySQL to script (INSERT statements, not live bulk transfer upload)

The same error was encountered while attempting to convert a Microsoft Access database that was derived from origin #1 above via MySQL Connector/ODBC 3.51 and the Access program's 'Import' function.

I will attempt to upload the MySQL Migration Toolkit generated schema script file (modified to remove comments, empty lines and remove the parentheses brackets from the 'DEFAULT (0)' value to 'DEFAULT 0' as noted in bug report #26308)

Thanks for addressing this issue and for no-charge use of the excellent MySQL Migration Toolkit. Off-topic: I posted some tips garnered from my own experience that if useful to other users would be welcome inclusions to augment the MySQL Migration Toolkit documentation. As a fellow software developer I am well aware of the difficulty to anticipate various real-world issues encountered by the end user and gaps in the documentation.

I forgot to include the URL for my forum content contribution regarding tips for converting a MS-SQL 2005 database.

http://forums.mysql.com/read.php?104,181246,181246#msg-181246

Thank you for the feedback. Could you please provide the Access file which
provoke the same error?. Thanks in advance.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Pardon me, but this continued requests for additional supporting evidence is ridiculous. I am not willing to invest more time to provide you with a second "Access" database. This issue associated with 'DEFAULT (0)' value to 'DEFAULT 0' as noted in bug report #26308 has been reported by several individuals for quite some time now and has never been addressed despite being acknowledged and confirmed. Since I have no intention to purchase a MySQL commercial license due to the issue, I can't be insistent. The #26308 fix is simple and would require far less time than just a fraction of the resources invested for the endless dialog.

This is a duplicate of Bug #26308, it seems.