[peterlaursen]

We did change the SSH tunneller client code (PLINK) with SQLyog version 5.15 to the latest stable version available. We did so to solve some reported issues with problems establishing a SSH-tunnel to recent FreeBSD versions.

We have reports that the new code has solved issues. But we also have a few reports like yours here. Frankly it looks as the new code has as many issues as the old one.

As a first measure I can give you a link to 5.14. I am 99% sure that this version will behave exactly as 4.1 with SSH-tunnel. Actually I would ask you to try it, so that we can verify that this is the issue. We will need a few days to find a 'strategy' for working with this.

Please create a ticket and I'll give you the link.

Finally I want to say that we did not have any problems with SSH or any machine/server (and that is dozens) that we have the option to connect to. We tested on each and everyone before releasing SQlyog 5.15. So if we can have access to some server where that problem is it would be nice too!

[peterlaursen]

I think that this ODBC driver cannot handle views!

That is one reason why I personally use Open Office Base (that can connect with JDBC – and here VIEWs work fine) if I need printing facilities for instance.

Maybe MyODBC 5.04 will work with Views. It is supposed to! the README tells:

“The short term plan is to have C/ODBC v5 support all major features of the existing C/ODBC v3 driver as well as flagship MySQL-5.0 features including stored procedures and views.”

I do not know Access 2003, but I doubt that 2000 and 2002 will ever be able to understand VIEWs.

MyODBC 5.04 is an alpha. I tried 5.02 and that was not easy to install!

But looks like 5.04 is improved in this respect!

http://mysql.com/downloads/connector/odbc/5.0.html

[peterlaursen]

We need more precise information!

The mapping 'proposed' by the wizard (including indexes, defaults etc) is as the ODBC layer on the source returns it when queried about it through the ODBC driver. It may even vary with differenct ODBC driver versions 🙁

We will need

1) Exact description of Source versions and ODBC driver versions

2) A 'create statement for the table' in some unambigious form (SQL, graphics)

3) A jobfile as the Wizard generates it by default and how you would have expected it to be!

Please keep the test case as simple as possible!

Is the Primary Key and the Key that auto-increments the same on the source server or is it two diffrent KEYs ? (some systems allow for that)?

You can create a ticket and attach data here if you do not wnat to expose it public.

[peterlaursen]

Quote:

Definition mismatch for 'ID' column in '`cm_approvers`' table … one-way replication to an *empty* target database.

What are the MySQL versions and what TYPE is column 'ID' ?

FULL definition for 'ID' please (NULL/NOT NULL … DEFAULT .. everything!! )

[peterlaursen]

It will do no harm to run the 'mysql_fix_privilege_tables.sql' script! And I think you should in case that the people that you hired did not. You will get into big problems with SP's and VIEWS in particular if the grant tables has not been updated!

[peterlaursen]

Quote:

here's the password hash

*9F6D2F236AEFE75CB25D1962C28230F5DCDEE60C

The hash SHOULD be:

69c4a4d359c7dd6b

The hashing method/algorith changed with MySQL 4.1. The first way is correct for 4.1 mysql and higher.

Quote:

it modifies soemthing but the new password doesn't work

With what client does it not work? Do you get any error messages (why will we always have to ask this question?) ?

does this help?

http://webyog.com/faq/23_58_en.html

http://dev.mysql.com/doc/refman/5.0/en/old-client.html

Are you sure that you did run the update scripts after upgrading? How did you upgrade? Did you just copy the /datadir?

[peterlaursen]

We plan to implement support for all storage engines with 5.17.

With MySQL 5.1 we will query the information_schema.engines table

With earlier MySQL version we will parse the returns of an appropriate SHOW statement

.. all to get a list of the ENGINES available.

.. and if your system returns NDB as an ENGINE that is installed and active it will appear in the dialogues and dropdowns.

http://www.webyog.com/forums//index.php?sh…view=getnewpost

[peterlaursen]

I believe everything is fixed now!

[peterlaursen]

Back to the problem with ther error.

I think that your table-file must be invalid. Those Cobol/ISAM files are not really protected against that!

Does the Migration Tool mapping dialogue show the column twice? I think that could nbe the issue. Now when you enter a query it will 'take from first instance only'. Also your Cobol application will not care about the second instance – if finds the first and does not care about the rest.

Could you possibly confirm that?

[peterlaursen]

First: betas are not available when FINAL is out.

I'll look int the upgrade issue!

edit:

The free downloads should function now.

For PRO and ENTERPRISE just replace '515' with '516' in the link in the mail.

Got to find out how this mail is generated!

[peterlaursen]

Something seems broken! We will look detailed into it tomorow morning.

Font settings (tools .. preferences .. fonts) for data display should work with TEXT and BLOB, but it only has effect when you save!

We plan to introduce font settings for everything in 5.17! See the announcement in the 'News' section.

[peterlaursen]

Quote:

Is it possible when importing with migration toolkit, to place a statement, to import only the most recent record of each article??

If you have a timestamp of latest change you can use it with SQL_WHERE

There is also the 'trigger' functionality:

links:

1-> http://webyog.com/faq/17_79_en.html

2-> http://www.databasejournal.com/features/my…p/10897_3550146

[peterlaursen]

We were in the process of changing links, upload new files for 5.16 FINAL, but found a cosmetical bug that took 10 minutes to fix.

Is it OK now?

[peterlaursen]

Hello!

Please read the post just below yours:

http://www.webyog.com/forums//index.php?showtopic=2265

I guess that the backup was made from MySQL 5 and you want to restore to an older version¨?

Read about sql_modes:

http://webyog.com/faq/28_72_en.html

You will need to edit the file a little!

[peterlaursen]

Now if you have a query like:

select id as id_targert bigint(20) NOT NULL auto_increment,

e eneum as enum_target ('yes','no') NOT NULL,

It think

select id as id_targert bigint(20) NOT NULL auto_increment,

e eneum as enum_target ('yes','no') NOT NULL,

PRIMARY KEY (id_target)

would work fine.

Doesn't it?

[Author]

Posts