[peterlaursen]

That happens because your MySQL server was incorrectly updated from a previous version.  Looks like you have upgraded from 4.x to 5.x ?/

After such upgrade you should always run the 'mysql_upgrade' program or the 'mysql_fix_privilege_tables.sql' script (is there is /scripts folder in your MySQL installation ?).  The installer does not run this script!  You will have to do so yourself.

Refer to: http://dev.mysql.com/doc/refman/5.0/en/upgrade.html

BTW: Also SQLyog User Management won't work unless the upgrade was done correctly.  The `mysql` database must be changed itself to be in accordance with the MySQL server binay itself.  That is what the 'mysql_fix_privilege_tables.sql' script does basicly: performs some ALTER TABLEs on the `mysql` database itself.

Note that this script (by design!) generates errors.  So you cannot run this script as an external file form SQLyog (it will abort with the first error).  You can copy-paste into SQLyog editor and run from her ('execute all') or you can run from command-line client.

[peterlaursen]

“Now, I have the old back up from August on my computer and want to merge it into the new data.”  That can be very tricky with such Forums.  I do not know V-bulletin in detail but I know this (IP Board) and phpbb2.  With both you will need to add post through the PHP interface of the application.  I do not think that V-bulletin is different.

What goes wrong is 

1) All 'counters' (no. of posts per member, last post per memebr, last visit of a memebr, number of posts in a topic etc. etc. etc.) will garble.  Whether you will be able to fix that manually I can't tell.

2) If there are autoincrement PK is in some tables (and I'd be surprised if there is not) you will have values having the same PK in both 'editions'  If you sync or import, the old values will be overwritten by the new ones.  And plain import will fail due to 'dublicate PK'.

SJA datasync is not a magician that can change the rules of the game!  

Did you ever read this:

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

To merge the two 'editions' of your Forums will take quite a lot of understanding of SQL, but most of all quite a lot of understanding of V-bulletin – and probably a lot of editing of the SQL files in a test editor.  I think you should absolutely have fixed the problem before letting members post again.

BTW:

1) the error message “No primary key found in table `posthash`” tells that there is no primary key in the table.

2) “Error No. 1064You have an error in your SQL syntax;”  not possible to tell what happens here – we will need some sample data to reporduce with.

[peterlaursen]

That is a good idea.

I just discussed briefly with a developer and we will try to implement 'refresh now' or 'force refresh' for every registered server individually.

Just FYI I'll describe two more problems/issues.

1)

Even if you change the server configuration the the values goes below critical threshold the red rectangle in the left pane does not go away. You will need to refresh the browser. That is a bug in the AJAX implementation, and it will be fixed of course.

2)

The MONyog 'real_refresh_rate' is the (refresh setting + the server response time + the transmission time) . Once we send a request we wait for the reply and only after having recieved that reply we start 'counting down' to send next request. With very short refresh interval and so-called 'slow servers' you will sometimes be able to see that they do not refresh at the same interval. The reason is of course that if we send a request before receiving the response of the first request that will cause problems in deciding which response matches which request – and it actully also cause some internal problems in the program too.

I do not think that adding (the server response time + the transmission time) to the user setting is an issue or a problem (in real life you will not use such short refresh interval), but if it is we will find a solution.

[peterlaursen]

It is fixed in the development tree. Next release will solve this.

[peterlaursen]

“I expect if you for example offer a hint for us, then I should have a button where if I click on it, to get in a way a copy in clipboard, or text for my.cnf in page somewhere.”

I am afraid that I do not fully understand. Currently MONLyog only connects to the MySQL server(s). We cannot have access to the file system like that when connecting to MySQL.

We do plan of course 'shell acces' to localhost as well as remote systems, but privilege to directly update the configuration file and restarting MySQL from a MONyog instance would probably not be given by the SysAdmin on most systems. Also what we give is not a non-disputable truth – it is an advisor only. For instance if more programs (like a webserver) is running on the same computer the SysAdmin may want/need to 'compromise' to balance the performance of each.

I agree that the hints could be more 'direct' like “insert this-and-that in the mysql configuration file [mysqld] section”. Also copying this into clipboard is a good idea.

[peterlaursen]

Rightclick somewhere in the reulst tab, export as …

What is your program version?

[peterlaursen]

Quote:

it still didn't work

Please explain the problem in detail and what you have been doing till now.

[peterlaursen]

SQLyog/SJA is the client.  All what is needed to connect to the servers (whether running on localhost or elsewhere) is compiled into the SQLyog***.exe and sja.exe executables.

Did I understand the question right?

[peterlaursen]

we know this of course. And it will be fixed too.

One workaround is to display a 'dummy' server at the right – simply by selecting a server twice

[peterlaursen]

Not difficult to understand! It was one issue while we were developing and we know this issue.

Basically you are supposed to move the mouse!

But we are considering different solutions.

What does “loop until “hell freezes over”” mean ??

[peterlaursen]

And ist should be (for a 4.0.x server) like this:

Select_priv

Insert_priv

Update_priv

Delete_priv

Create_priv

Drop_priv

Reload_priv

Shutdown_priv

Process_priv

File_priv

Grant_priv

References_priv

Index_priv

Alter_priv

Show_db_priv

Super_priv

Create_tmp_table_priv

Lock_tables_priv

Execute_priv

Repl_slave_priv

Repl_client_priv

ssl_type

ssl_cipher

x509_issuer

x509_subject

max_questions

max_updates

max_connections

As I wrote in your ticket you should run the fix-privileges script.

Looks like this server has been (incorrectly) upgraded form 3.23.x

[peterlaursen]

We will improve sorting and filtering a lot in 5.3 .  You will proably see the first beta in a couple of weeks.

You cannot as of now:

* sort on more than one column in the DATA tab

* sort from the RESULT tab at all

[peterlaursen]

I do not think you will find any GRID based client for nay database server doing this.  They read from the GRID as SQLyog do (with the the 'smart' keywords and functions as a special featue of SQLyog).

You should start doing a

SELECT allthefieldswhereyouhaveprivilege FROM …..

Now a RESULT tab will open showing only those fields and the update statement will only use these fields in the SQL statement

[peterlaursen]

“show full fields from sometable” executes when one resultset is in 'edit'mode (not showing 'read-only' in the dropdown). But there is nothing new in this RC compared to earlier releases in this respect. It is a coincidence that you encounter this now.

The internal code processed in 'edit'mode and 'non-edit'mode is not quite the same.

But 'database does not exist' should not occur if it does exist, of course.

We continue with this tomorrow.

[peterlaursen]

reproduced now, but we still don't have a clew!

[Author]

Posts