[peterlaursen]

We simply are running out of ideas of how to do progress here. Do you have any?

[peterlaursen]

wondering if it is this issue:

http://code.google.com/p/sqlyog/issues/det…5&start=100

Please tell what you know about this server!

[peterlaursen]

I am sorry, but 'time flew' for us today. We will definitely pay attention to this tomorrow morning!

[peterlaursen]

1) could you please attach that dump file here?

2) If you can connect with some other client please execute “SELECT VERSION();”. What does it return?

(it is important that you do execute this and paste the result exactly as returned!)

[peterlaursen]

version 6.12 RC was released!

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

Everyone who has installed the non-public release linked to above, should replace as the non-public build could easily crash immediately after establishing HTTP-connection.

[peterlaursen]

You may have noticed allready that we in fact save to user's 'AppData' folder. So every user will have his personal sqlyog.ini.

[peterlaursen]

We cannot reproduce this. I create in one database, run struct sync, copy script to clipboard, close struct sync, select another database, paste the script into the editor and execute. Next run struct sync again. No differences found.

Forgive me if this is a silly question: do you understand the structure sync will generate a script that you will have to execute later? Running structure sync does not ITSELF exectue the sync script generated. You will have to do!

Also please tell if this stored procedure was created with an earlier (5.x) version? If so there might be some issue with how are represented. Can you copy the function definition from ALTER PROCEDURE from both databases, save both as text files, zip and attach here. It is important that it is attached as a binary (zip) file and not text files to avoid browser formatting issues!

[peterlaursen]

We fixed this issue with empty names!

Please confirm the fix with this build:

http://www.webyog.com/downloads/betas/not_…QLyog612Ent.exe

… and still please provide details for the other issue you reported!

[peterlaursen]

There should be no difference between the versions in this respect!

Could you try to have both installed at teh same time and try both once you experience problems.

It may be a coincidence that something has happend with the connection about the same time that you upgraded.

[peterlaursen]

Will this help: http://webyog.com/faq/content/23/18/en/err…on-denied-.html ??

Probably the user is not allowed to connect from remote hosts but from 'localhost' only.

two options:

1) configure user to connect from remote hosts

2) use SSH or HTTP tunnelling

[peterlaursen]

let me explain further:

the API has no functions (or nothing else similar) like

*StoredProcedureSetBreakpoint(…)

*StoredProcedureExecuteWithBreakpoints(..)

*StoredProcedureListVariables(…)

etc..etc. – what would be required to really debug inside the stored procedure.

… so basically you will need to write the SP with debugging code inside it, and remove/comment it once it is not required anymore!

But still ideas are welcome!

[peterlaursen]

@chris

1)

You are telling that structure sync of 6.11 still reports difference immediately after it executed?

please provide more details and an example!

2)

missing names is confirmed!

example:

create a dummy table in two empty databases and a dummy SP 'qwe' in one, sync from the one without the SP, check 'drop SP' from struct sync gui and run struct sync – script will be like (empty SP name):

Code:

/* Drop Procedure in Second database */

DROP PROCEDURE `test`.“;

[peterlaursen]

Currently you will need a job for every target.

[peterlaursen]

Please post SQLyog questions in the SQLyog – and not MONyog – category!

This has been asked before.The problem is that MySQL provides no API functionalities (classes, functions etc.) for that! There simply is NO WAY to really debug a Stored Procedure/Function/Trigger/Event in MySQL like in SQL Server, Oracle etc. In that respect MySQL is still very primitive compared to other databases!

There are a few other 'debuggers' that we have studied and non of them really debug the Stored Procedures. They 'simulate' a Stored procedure – for instance by using @user_variables with plain SQL instead of declared variables inside Stored Procedures. This will work with simple demo examples – and not much more!

I think it is now about 9 months ago we discussed this, and we did not find a solution. We will not provide 'eyecatch' that does not do the right thing. But ideas are welcome of course!

[peterlaursen]

BTW: this is a SQLyog question – not a MONyog one!

I am moving to SQLyog category!

[Author]

Posts