[weiliang]

Of course, every client have to use SQLyog in order to have version control feature.

We need this feature because we have several DBA developing stored routine and sometimes they are altering table definition. The situation is complex when we are trying to find out which routine and/or table definition is newest and bug fixed.

If SQLyog doesn't support this and won't support, do you have any recommendation how to overcome this. Thanks

peterlaursen wrote on Jun 3 2009, 04:45 PM:

We have request for integration in version control systems before and we have this recorded:

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

But your request is different. And impossible to implement. For two reasons:

1) SQLyog does not know what other clients are doing

2) A client cannot do this as the server does not expose such information for clients. The server has no records of objects history (unless exposed in the general query log and this will practically never be complete for objects history from the 'very beginning'). And a client cannot even read the general log (only an Operating System user can)-

What we *could* do was to implement some version control for SQL scripts handled by SQLyog. This will make good sense if SQLyog *alone* is used for development of a database application (but will fail if other clients than SQyog are used). But even this is not planned for near future.

[Author]

Posts