[peterlaursen]

That was reported internally a few days ago and fixed in beta3 that was released today.

It also works for me now.

Can you confirm the fix with beta3?

[peterlaursen]

I think that if it is an autoincrement column (and that also is a PK), it is very different actually. The idea with using a an autoincrement column is as this 'give me a unique number and as long as it is unique I really do not care what it is'!

Such columns are inserted by the server and the user/admin is not supposed to bother about the values …

Our own FAQ (powered by phpMyFAQ) is multilingual too, but here the design is that the PK is defined on TWO columns: the 'id' column and the 'lang' column. When a 'semidublicate' (same topic – another language) is created the application explicitly writes the 'id' as identical to the same post in the other language(s) – if it is a completely new topic the the application inserts (max(id) + 1) for the new id. I think this is a good design for multilangualism.

The table definition for the main table in this system reads:

CREATE TABLE `faq_faqdata` (

`id` int(11) NOT NULL default '0',

`lang` varchar(5) NOT NULL default '',

`solution_id` int(11) NOT NULL default '0',

`revision_id` int(11) NOT NULL default '0',

`active` char(3) NOT NULL default '',

`keywords` text,

`thema` text NOT NULL,

`content` longtext,

`author` varchar(255) NOT NULL default '',

`email` varchar(255) NOT NULL default '',

`comment` enum('y','n') NOT NULL default 'y',

…

…

PRIMARY KEY (`id`,`lang`),

FULLTEXT KEY `keywords` (`keywords`,`thema`,`content`)

) ENGINE=MyISAM DEFAULT CHARSET=latin1

[peterlaursen]

I will ask the MONyog team to look into it!

[peterlaursen]

no .. that is not normal, and should not be like that!

Please tell the exact program version and also please attach a screenshot that illustrates it!

[peterlaursen]

finally we were able to release beta3

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

Please verify the fix for this!

[peterlaursen]

With SQLyog you will have to execute

* structure sync

* data sync

in that order

“I don't want to run all the updates one by one.

I saw there are 2 tools in the SQLYog – structure compare and DB sync which may do the job but in many steps”

>> no in TWO steps – not MANY steps

I want to create a diff script automatically that will upgrade the production schema.

>> structure sync will 'generate a script', data sync will not 'generate a script'. data sync if implemented in the SJA, that is a compiled binary. BINARY .. not SCRIPT.

[peterlaursen]

Could you explain what prevents this developer to

1) first run a structure sync from test machine to production machine

2) and next run a datasync

(and possible also a FTP sync to sync files if required)

.. that also is what a lot of web developers are doing!

The point I see is that also for data sync you want to preview and accept every change?

[peterlaursen]

I am not sure, but I think those issues are caused by the MySQL server and not MONyog.

What is returned from the server if you manually issue 'SHOW FULL PROCESSLIST' ?

[peterlaursen]

but I understand that you want to be able to 'preview changes'?

I can add such 'feature request' to our issue tracker, but it will not be priority for some time to come!

[peterlaursen]

Currently not. Is that important for you? I think it would not be hard to change the hard-coded constant to a configurable setting!

[peterlaursen]

we will of course take your comments 'ad notam'. We also will add features to data sync in the future. Requests and comments are always welcome.

However comparing data may be useful for a few changed rows – but what would you do if x*1000 or x*10.000 rows (or even x*100.000 rows) had changed/had been inserted/deleted since last sync? Would you be able to compare everything before allowing the sync to proceed?

I think rather the solution is to add more 'conflict resolving rules' (our task) and to structure how the databases are used (users'/DBadmin's/application programmer's task).

[peterlaursen]

to grant privileges for VIEWS in a single database (or a single view only)

tools menu .. user manager .. manage permissions

select the database and define privileges by checking SELECT (and whatever) for the databse itself in the uppermost window or for specific view(s) in window no. 2 from above

tools menu .. user manager .. add/edit user is for defining user name, password and GLOBAL privileges

tools menu .. user manager .. manage permissions is for defining OBJECT SPECIFIC privileges

so if you want only OBJECT SPECIFIC privileges for this user, nothing shall be checked in add/edit user!

Attached image shows a TABLE 'notes' and a VIEW 'notesview' in the 'test' database. SELECT privilege for the selected user is defined on 'notesview' but not on 'notes' and not on any other tables or views either!

[peterlaursen]

You should use the DATA synchronisaton tool .. not the STRUCTURE synchronisation tool .. to synchronize data for the databases on the remote and local server.

Additionally you should use a FTP synchronise tool to synchronize file attachments.

You may study this article on SQLyog data sync:

http://webyog.com/en/sqlyog_data_sync.php

and here you will find FAQs about data sync and the SJA in general:

http://webyog.com/faq/category/11/mysql-da…ronization.html

http://webyog.com/faq/category/25/sqlyog-job-agent-sja.html

Please study a little .. and feel free to ask specific questions!

[peterlaursen]

I think we will plan in detail for analysis of historical data/trends by mid or end next week.

Defining and comparing 'snapshots' would absolutely be relevant!

[peterlaursen]

No – I am confusing this with an issue with MONyog on 64 bit Gentoo.

Do you have full 32 bit support installed?

(we have tested on Ubuntu 64 with 32 bit support installed and had no issues). Now we have replaced the OS on that machine with a Fedora 64 bit.

It is very hard for you to debug such thing .. practically impossible I think. It is a compiled binary, not a script.

Test case and/or temporary access to the server(s) would be best solution

[Author]

Posts