UniDump problem with MySQL4

Discussion of open issues, suggestions and bugs regarding UniDAC (Universal Data Access Components) for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
redone
Posts: 6
Joined: Fri 18 Jan 2013 11:46

UniDump problem with MySQL4

Post by redone » Thu 16 Jan 2014 16:44

Hello,

i use UniDAC 5.2.5 with XE5. When i use Unidump with MySQL4 there is no CREATE TABLE in the dumpfile. Instead CREATE TABLE there is ?????????????†?????????????????????†?? written.
Options of UniDump:
AddDro
CompleteInsert
GenerateHeader
QuoteNames
all true

SpecifiedOptions
BackupTables
BackupViews
UseExtSyntax
on true

InsertTyp = itInsert

How can i fix the problem?

redone
Posts: 6
Joined: Fri 18 Jan 2013 11:46

Re: UniDump problem with MySQL4

Post by redone » Fri 17 Jan 2014 10:44

Hello,

the same in Delphi7 tried, no problems.

hh-cm
Posts: 6
Joined: Fri 23 Aug 2013 16:08

Re: UniDump problem with MySQL4

Post by hh-cm » Sat 25 Jan 2014 16:59

I have the same problem. Any news on this?

hh-cm
Posts: 6
Joined: Fri 23 Aug 2013 16:08

Re: UniDump problem with MySQL4

Post by hh-cm » Fri 31 Jan 2014 11:56

By the way,

it occurs only in DirectMode. With libmysql its ok.

PavloP
Devart Team
Posts: 149
Joined: Fri 24 Jan 2014 12:33

Re: UniDump problem with MySQL4

Post by PavloP » Fri 31 Jan 2014 14:58

Please provide the script for creating the table, on which the problem can be reproduced, and specify the exact MySQL version

hh-cm
Posts: 6
Joined: Fri 23 Aug 2013 16:08

Re: UniDump problem with MySQL4

Post by hh-cm » Sat 01 Feb 2014 08:26

MySQL Version : 4.1.22-community-nt

Code: Select all

CREATE DATABASE IF NOT EXISTS `dumptest` /*!40100 DEFAULT CHARACTER SET latin1 */;
USE `dumptest`;

CREATE TABLE IF NOT EXISTS `test` (
  `Column 1` varchar(50) default NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
The result is

DROP TABLE IF EXISTS test;
???????????†?????????????????????????????????????;

PavloP
Devart Team
Posts: 149
Joined: Fri 24 Jan 2014 12:33

Re: UniDump problem with MySQL4

Post by PavloP » Tue 04 Feb 2014 12:19

Thank you for the information.

We have reproduced the problem and fixed it.

This fix will be included in the next UniDAC build.

Post Reply