We will provide SSH tunnelling to MySQL on the remote host soon. Untill then you will have to use a 3rd party application to establish a SSH-tunnel. But with a 'dedicated server' I think it should be possible to open a MySQL port and allow in MySQL configuration to use it!
You should not compare MONyog with phpMyAdmin (or 'Query Browser' from MySQL AB or our own SQLyog for that sake). Those are for managing DATA primarily – not the server ENVIRONMENT. 'MySQL Administrator' from MySQL AB does display server configuration variables and status but only statically and provides no advisors (but it is a nice program to have for not so experienced users who want to change configuration – and most of all to get an overview of what configuration parameters are available!). Also MONyog lets you view and EXPLAIN queries in real time and more like that (including analyzing the SLOW QUERY LOG) will be added in the next about 2 months.
4)
MONyog is preferable for
1) performance and architectural simplicity
2) pricing and license terms (perpetual license – no annual/periodic subscription fee)
This is a SQLyog question, not a MONyog question. Please post in the correct category. I am moving you!
I can confirm that there is some issue. Also when connecting to a table with 10.000 rows and a LIMIT setting of 100, 6.1 is much slower than 6.07. What seems to indicate that the full table is loaded!
Maybe you noticed that the 'preferences' dialogue was rearranged. I think it could be a bug related to that, even though HISTORY tells that LIMIT is used. The statement from HISTORY executed from the editor in 6.1 seems to be as fast as is the 6.07 GUI.
It is Indian holiday today and we will only be able to get closer tomorrow.
Also note that a specifically SSL-enabled user is required for this (a MySQL user is either a SSL user or not – he cannot be both! Refer to GRANT syntax description in MySQL docs).
There are programs in practically every unix/linux 'dialect' to build SSL ceertificates. No need to pay for it!
Alsos note that SSL certificates will expire and need to be renewed!
2) Also SSH is an option with Windows.
The free OpenSSH package works fine on 2003 – however it is a little more tricky to set up on this system compared to 2K/XP.
your applications don't use BLOBs/TEXTs extensively?
(it is a common problem with 'standard' PHP applications like this Forums for instance. If so there is not much to do – except hoping that the developers of such software will use MONyog on their test servers to optimize their software!)
(select location_id from patient_transactions where location_id) = 7
then
select (sum(account_tot)) as office from patient_transactions where location_id = 7
when
(select location_id from patient_transactions …. ) = 46
then
select (sum(account_tot)) as inpt from patient_transactions where location_id = 46
when
…
then
[else …]
end
I think it must be something like this above you are looking for. But I do not fully understand!
In particular I am not able to understand what is the idea with the GROUP BY!
And basically I doubt that the CASE solution is the solution to your problem.
Why not simply
select (sum(account_tot)) from patient_transactions group by location_id;
— to me it seems as if the only reason for the CASE is that you want a different alias for every sum depending on the location_id.
Why not store this alias in the database itself for very value of 'location_id'?
Using a 'parent table' and including this with a JOIN type query seems to me a more logical design! It seems that you are trying to solve IN CODE what should be solved in DATABASE DESIGN.
SELECT CASE WHEN (select 9999) = 0 THEN 'new math arrived' WHEN (select (0<1)) THEN 'it's a hit' ELSE 'I give up' END;
SELECT CASE WHEN (select 9999) = 0 THEN 'new math arrived' WHEN (select (0>1)) THEN 'it's a hit' ELSE 'I give up' END;
SELECT CASE WHEN (select 5+2 = 7) THEN 'same old story' WHEN (select (0<1)) THEN 'it's a hit' ELSE 'I give up' END;
(note that both “(select 5+2 = 7)” and “(select (0<1))" are true - but the statement exits 1st time a condition is satisfied)
Also you can use 'case values' after CASE like
SELECT CASE 7 WHEN (2+5) THEN 'same old story' WHEN 4+3 THEN 'it's a hit' ELSE 'I give up' END;
SELECT CASE 7 WHEN (4+3) THEN 'it's a hit' WHEN (2+5) THEN 'same old story' ELSE 'I give up' END;
(and again the statement exists 1st time a condition is satisfied)
more:
SELECT CASE 2+6 WHEN 4+3 THEN 'it's a hit' WHEN (2+5) THEN 'same old story' ELSE 'I give up' END;
SELECT CASE (select 2+6) WHEN 4+3 THEN 'it's a hit' WHEN (2+5) THEN 'same old story' ELSE 'I give up' END; –identical
SELECT CASE select 2+6 WHEN 4+3 THEN 'it's a hit' WHEN (2+5) THEN 'same old story' ELSE 'I give up' END; –oops 🙂 can't resolve this!
SELECT CASE (select concat('a','b')) WHEN 'ab' THEN 'it's a hit' WHEN 'xy' THEN 'no .. you won't fool me' ELSE 'I give up' END; — case value need not be a number
SELECT CASE (select concat((select('a')),'b')) WHEN 'ab' THEN 'it's a hit' WHEN 'xy' THEN 'no .. you won't fool me' ELSE 'I give up' END; — not number here either
SELECT CASE (select concat(select('a'),'b')) WHEN 'ab' THEN 'it's a hit' WHEN 'xy' THEN 'no .. you won't fool me' ELSE 'I give up' END; — oops again!
but why “CASE (select 2+6) …” and “CASE (select concat((select('a')),'b') ..” works and not “CASE select 2+6 …” and “select concat(select('a'),'b') ..”
.. well, ask MySQL AB. Just to point out that your header “CASE in SQLyog” is wrong actually! CASE is implemented in the server – not the client, so correct would be “CASE in (My)SQL”
You can use CASE as a 'Control FLow statement' (SELECT CASE …) or you can use CASE inside (between BEGIN .. END) a Stored Procedure, Function, Trigger or Event ('stored program') The syntax is slightly different.
I am not sure I got your point, but it makes no difference if you run two one-way syncs or one two-way sync, if only you define source and target appropirately!
A two-way sync will first sync source>target and then target>>sync.
The only difference is that with two-way it will be done for every table before proceeding to the next table.
“The trial version allows me to choose only one table at the time” no .. TWO!
“The result is that the source db overwrites the target db” This is by design!.
Please search a little! This has been asked 100 times and replied to 100 times as well!
Short answer: there is NO WAY a computer can tell which row is the correct one if two rows with the same PK_value exists on both hosts, it needs a 'rule' defined by a human. The only 'rule' supported at a time is “overwrites ” We plan a more advanced 'conflict resolver' for users to define their own rules.
I think the reason simply is that the constraint name is allready in use! You can only use a constraint name once in a database.
SQLyog will 'propose' a constraint name generated from the 'child' table name. If you have more than one child row in a table you will need to enter a constraint name of your own choice.
Author
Posts
Viewing 15 posts - 3,676 through 3,690 (of 7,398 total)
peterlaursen
Participant
