[peterlaursen]

I added your request here:

http://code.google.com/p/sqlyog/issues/detail?id=431

did I get every detail correct?

[peterlaursen]

additional:

You may create a ticket if you want privacy.

It also would be nice if you would allow us to connect. You only need to create a user with NO privileges!

[peterlaursen]

I think it does!

the first link:

“This also applies to the DEFAULT value settings of the CREATE TABLE and ALTER TABLE panes and the MAPPING option of the Migration Wizard when using the three of the above KEYWORDS that may be used as a column DEFAULTs (they are NULL, CURRENT_TIMESTAMP and localtimestamp). “

so the KEYWORDS NULL, CURRENT_TIMESTAMP and localtimestamp can be useed for column defaults. Functions cannot – except for now() that is internally represented as a synonym of CURRENT_TIMESTAMP.

[peterlaursen]

Please read:

http://webyog.com/faq/content/8/99/en/does…l-keywords.html

http://webyog.com/faq/content/8/116/en/can…sult-panes.html

[peterlaursen]

ok .. a colleague told me that I probably misunderstood!

Please read: http://webyog.com/faq/8_116_en.html

If 'smart keywords' is turned ON in 'preferences' SQLyog will try to evaluate the function!

Two ways to avoid

1) Turn smart keywords OFF.

2) use `backticks`around the string like `concat(a, b )` and it will be considered a literal and not a function that should be evaluated

[peterlaursen]

This is to my best understanding not a bug!

The concat() functions takes strings as arguments! Unless they are string columns or declared variables inside a stored program (stored procedure, function, trigger etc), a and b will not be recognized as strings by the server.

The error message is sent from the server and would be the same with any client.

Why don't you write concat('a','b')? What point am I missing?

[peterlaursen]

I think the issue is that you have a local MySQL server version 4.1 and higher, and the hosted server is 3.23 or 4.0. The latter versions do not support comments.

We have a similar request to have an option to provide 'fully 4.0 compatible backups' from higher version. There is no such option currently.

If you connct to both servers at the same time you can use 'copy to other' or 'data sync' – they will work across versions. But if you cannot connect to the remote host with direct connection, you will need HTTP-tunnelling or SSH-tunnelling – what is only supported with ENTERPRISE.

Give the ENTERPRISE TRIAL a try? For a setup with a test/development server and a production server the STRUCTURE and DATA sync tools of SQLyog ENTERPRISE will save you lot of time.

[peterlaursen]

After installing on the new machine, you copy the sqlyog.ini file from the old machine.

In older versions the file is in the installation folder

In the most recent versions the file is in users 'Application Data' foler

[peterlaursen]

“So there will be a generic Tunnel'er that any desktop application can connect to it?”

We would like to do it but did not find resources to start working on it yet.

“a. Is the above possible with just the SQLyogTunnel.php ? I am assuming No, from the Thread (Above)

b. Will the Generic Tunneller application allow any desktop app to connect.

c. Can/could the SQLyogTunnel.php be tweaked to meet my needs in the meantime? After purchasing the Enterprise (of course)… “

a: you are right in assuming no!

b: the idea was that this application should communicate with connecting applications exactly as the MySQL server does with a direct connection. To the extend that is possible (and I believe it is), the answer is 'yes'.

c: no. The application (whether SQLyog, SJA or such 'generic tunneller') communicates with the PHP tunneller script using an XML format. A application is needed with 'built in knowledge' of all details (including how data types are identified) of this format. So there is no need to tweak the SQLyogTunnel.php (a 'generic tunneller' could in principle use exactly the same tunneller script on the server as SQLyog does) – it is an application to be executed on your local machine that is needed.

[peterlaursen]

That is a very reasonable request!

Added here:

http://code.google.com/p/sqlyog/issues/detail?id=427

[peterlaursen]

Right-click the table in the Object Browser .. reorder columns

[peterlaursen]

Actually we have a pending request to provide an option NOT to include definer for VIEWs and SPs:

http://code.google.com/p/sqlyog/issues/detail?id=324

[peterlaursen]

Ok .. now I understand.

Agreed – we have inconsistences! With the 'definer' clause, as well as the 'SQL_SECURITY' clause.

For TRIGGERS the 'definer'clause is not shown (it is for VIEWs and SP's)

The 'SQL_SECURITY' clause is shown for VIEWs only .. not other objects.

When we introduced support for all those objects the two clasues were both not introduced in MySQL yet. The support that we added later is far from complete and sufficient. That is the history of it.

Actually I think in some situations it may cause problems to include those clauses and in some other situation it may cause problems NOT to include them .. so this should be an option ideally. We will need a little time to discuss the solution in details, but we will include improved dialogues/GUIs for exports, copy and structure sync in the 6.2 tree.

Thanks for reporting!

[peterlaursen]

true

The database (keywords.db) user for autocomplete and syntax highlighting is not complete for the latest MySQL versions. Keywords are not version specific either. This is planned for version 6.2.

About NEW and OLD keywords

http://dev.mysql.com/doc/refman/5.0/en/using-triggers.html

“The OLD and NEW keywords enable you to access columns in the rows affected by a trigger. (OLD and NEW are not case sensitive.) In an INSERT trigger, only NEW.col_name can be used; there is no old row. In a DELETE trigger, only OLD.col_name can be used; there is no new row. In an UPDATE trigger, you can use OLD.col_name to refer to the columns of a row before it is updated and NEW.col_name to refer to the columns of the row after it is updated. “

But you can add your own keywords – refer to

http://webyog.com/faq/content/8/93/en/can-…o_complete.html

And if it is very importabt for you we can of course add those two with 6.1 FINAL too!

[peterlaursen]

I think the problem is different MySQL versions!

When triggers were introduced in 5.o there was no 'definer' clause. It was added later.

Please tell the MySQL versions involved!

[Author]

Posts