[peterlaursen]

okokokok …

[peterlaursen]

To me the upper bound of the two examples (connections dialogue, screen properties) look the same. I cannot see any delineation issue. Maybe there is a display issue on you monitor, but once captured to clipboard and saved as a file there is no issue as far as I can see.

Please have a look a the files yourself!

If I am blind please help compensate it by drawing an arrow pointing to where I should look (or something like it!)

[peterlaursen]

Now … quite some time has passed since version 5.21. This verson was one of the first Open Source releases and there were some what we call 'refactoring bugs' in there.

The memory of the radar has expired. A new image of the enemy has to be spotted! 🙂

We have to concentrate on the 6.x code tree! For the simple reason that if there was and still is an issue we cannot 'fix backwards'. Only in future versions we can!

Could you upgrade to latest 6.x build? Or install the 6.x trial? If both are not possible please create a ticket and we will find a solution!

[peterlaursen]

The default setting is 50 characters. Did you change it?

[peterlaursen]

We cannot reproduce and don't understand how that error could occur here.

If you (either of you) could let us have temporary access to the server(s), then please create a ticket, so that we can exchange details.

We could also give acces to some server of ours so that you could check if it happens for you on this server.

[peterlaursen]

@Syphondex

please answer:

1) is it happening with all kinds of connections or only some specific type (like SSH, HTTP)

2) is it happening with every server (in case you have more) or only a specific one.

3) is it 100% consistently reproducable, or does it happen 'randomly' ?

[peterlaursen]

Please confirm: The issue with the connections dialogue is only that the image does not 'fill out' the rectangle area reserved for it?

I think bitmaps are not affected by DPI settings. They are always displayed as x*y pixels, it seems!

[peterlaursen]

You are right. We have only tested on 'normal' DPI setting. Is it 'standard high' or a 'custom high' setting you are using?

We do plan to improve 'adoptability' to various screen resolutions, types and settings, but I cannot guarantee about this one.

Anyway I will ask the team to check tomorrow – it looks like a few pixels more is what we need here!

Other places in the program with same issue?

However, actually I was checking the setting in Vista, and it seems that Microsfot has removed it. Corrrect me if I am wrong!

See attached image for 'normal DPI' display.

[peterlaursen]

Using a multicolumn PK specific for each host will work!

This trick was actually mentioned here too:

http://webyog.com/en/whitepapers/Using_SQL…L_Databases.pdf

But there are som limitations. If you want to DELETE you willl have to do on all computers, and you can only do UPDATE on a row on one computer between syncs.

Scroll down to the paragraph 'Making the PK host-specific' for details.

Syncing will sync complete rows (or 'records') and of course rows that are identical on the two host at sync time will of course not be touched.

[peterlaursen]

I see you are using version 5.19.

I think you should first try a later version. Could you install the latest trial. If you had a trial installed before and it has expired, then please create a ticket and we will find a solution!

You don't experience the same with large batch jobs like imports?

[peterlaursen]

Right-click in the RESULT tab and the context menu will give you export options.

Did I understand right?

[peterlaursen]

The basic problem is (as explained lots of times now) that when data differs on either host, ther is no way for a couputer to tell which ones are the 'correct' ones. A 'rule' must be defined by a human.

Currently we only support the rulge: 'source overwrites target'.

@crhockey – what rule could help you here? 'latest data take precedence' or something else?

[peterlaursen]

You cannot export to .xls with SQLyog. The SQLyog EXCEL export uses the Excel 2003/2007 XML-based format. You can open it in an editor (like Notepad) and see if data were truncated during export or if is Excel that truncates data during import.

Now

1) attach a sample exported file

2) generate a table using the same query (“create table tablename select …”) and dump that table and attach here.

(and please zip files)

[peterlaursen]

1) Please refer to the beta1 release notes: From 6.06 beta 1 the .ini file is no longer read from installation folder but from user's 'application data' folder.

2K,XP,2003: /documents and settings/user/application data/sqlyog (i think, but currently I only have Vista available!)

Vista: /users/user/AppData/Roaming/SQLyog

(note that folder names may be localised/non-english)

First time the program is opened after install of 6.06 the .ini, .err and .log files are copied to the new position (and a backup left in original position). Did that copy process fail for you? We have tested it VERY MUCH and have no other reports of such failure!

2) I think we should try to reproduce with a so-called 'slow connection'- it might be a buffer that runs over if user is faster than the connection!

Is it a SSH-connection that you use when reproducing or any kind of conenction?

[peterlaursen]

now two issues left:

1) the crash that is clearly reproducable for you but not for us.

2) enable reconnect in structure sync

[Author]

Posts