Forum Replies Created
-
AuthorPosts
-
peterlaursen
ParticipantI think your initial post and the dump do not quite correspond. Table names are not the same! So i have a little trouble identifying exactly what the FK's should look like!
But I think the two *VOL_id's and the two *IM_id's ??
This
KEY `LNKIM_id` (`LNKIM_id`,`LNKVOL_id`)
will not work, I think. I think you will need a seperate key for every column like
KEY `LNKIM_id` (`LNKIM_id`),
KEY `LNKVOL_id` (`LNKVOL_id`),
but even after that change I too can only create ONE (and any) of the FK's
I am also wondering what I am missing ….
peterlaursen
ParticipantI think you should attach a structure-only dump of the tables involved.
Are you sure that datatypes are matching? Trying to create a FK on string columns with different collations … lots of possbilities!
peterlaursen
Participantno .. not wrong. There are always PROs and CONs with any GUI design.
In terms of SQL implementation we would then have to send a USE statement when a specific Query tab is clicked. That could be done, and we could relatively easy implement some kind of a 'properties' dialogue for a Query tab.
We should then optimally as well change the display of the selected database in
* the dropdown where selected database displays
* the Object Browser
when a Query tab is clicked.
If you noticed: when you select in OB the dropdown changes, but when you select in dropdown OB display does not (it is the dropdown that 'counts')! There are some coding difficulties here that have not been solved. If a Query tab should SIGNAL change-of-database to the other GUI elements then it get even more complicated. But of course complications is no excuse!
I think we will need to discuss this! We will relase 6.1 beta 1 shortly and after that we can get some air for discussing new ideas.
peterlaursen
Participantgood point!
the 'parent' of the DATA tab is the Object Browser.
the HISTORY tab is 'child' of every Query tab that has been opened since connection was established
all other TABs have the selected Query TAB as 'parent'.
Actually .. with hindsight .. it would be more logical if the DATA tab was the 1st/leftmost tab (as close to the Object Browser as possible) and if some graphics clearly indicated this parent/child structure!
September 25, 2007 at 7:27 pm in reply to: Error 2013: Lost Connection To Mysql Server During Query #25023peterlaursen
ParticipantIf it is COMMUNITY version it is direct connection!
if it is EXACTLY 20 minutes it looks like a time-out setting on the server/the remote network or some networking gear.
if it is more RANDOM it simply may be the connection that is not very stable. Could you try from another location (home/office/a friend/whatever)
peterlaursen
ParticipantI replied in your other topic!
What some other program does does not matter if it is wrong!
A query in MySQL (and therefore not a query tab either) is not restricted to access a single database!
I think instead we should 'push' the request (by other users and me!) to rename a Query Tab. It could be an option that the query tab gets named from the selected database at the time of creation (like 'query.1stdatabase.1','query.1stdatabase.2','query.1stdatabase.3','query.2nddatabase.1' etc)
If 'linking' means restricting access to other databases we won't!
peterlaursen
ParticipantA Query TAB can contain queries using more than ONE database (actually a single SELECT can).
It is not possible to 'link' a specific Query TAB to a specific database in the Object Browser.
I suggest you add a comment at the top like
— must use some_database
What you should understand is that the selected database is the latest one one specified with a USE statement.
When you work on that database you won't need to use full syntax like `database`.`table` ; `table`alone will do.
I do not see how this request can be implemented.
September 25, 2007 at 6:11 pm in reply to: Error 2013: Lost Connection To Mysql Server During Query #25021peterlaursen
ParticipantBasically if you want us to help with that you should upgrade to the latest stable version and verify if the problems persists.
Whatever issue there might be, we can only possibly fix issues in FUTURE versions – not in PAST versions.
But the connection type (direct, HTTP or SSH) would probably be relevant information to give!
peterlaursen
Participantconfirmed!
test case:
CREATE TABLE `test` (
`n` int(11) NOT NULL,
`t` varchar(5000) default NULL,
PRIMARY KEY (`n`)
)
INSERT INTO test (t) VALUES — t is a varchar(5000)
('aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaabbbbbbbbbbcccccccccc'); — 500 a's 10 b's 10 c's
select t from test;
— in DATA TAB and RESULT TAB GRID mode only ONE 'c' is displayed
— in RESULT TAB TEXT mode ALL 'c's are displayed
Basically this is a MySQL 5.0 compability issues that we did not fix. Before version 5.0 MySQL varchars could be only 255 characters.
We should provide an option for user to define the length of string (no matter the type) that should open in the BLOB viewer. For most users I think even a string 100 characters long is too long for the GRID.
Actually it has been here:
http://webyog.com/faq/content/33/20/en/pla…-of-sqlyog.html
.. for long. Always was given 2nd priority!
In the short term we should consider to raise the max witdh of the cell to around 65.600 (if it can be done with the GRID code) to support mySQL 5.0 LONG varchars
September 25, 2007 at 3:00 pm in reply to: Bug Or Feature? Ssh Connection Tab. Password Always Needed #24984peterlaursen
ParticipantYes – the PLINK shipped with SQLyog is a special build.
I do not understand either why “-P 22” is wrong when P defaults to 22?
peterlaursen
ParticipantWe will provide an option to analyze the SLOW LOG from inside MONyog soon.
With version 1.1 (beta1) we support SHOW FULL PROCESSLIST from inside MONyog and you can monitor the queries in real time, and EXPLAIN them.
Please refer to the 1.1 beta1 release notes: http://www.webyog.com/forums//index.php?sh…view=getnewpost
peterlaursen
ParticipantIf there is no “local-infile” in the MySQL configuration file it is by default enabled.
MA did not realise that! And it did the opposite of what the GUI told!
Besides I do not remember that old discussion in details any more.
The '0' and '1' settings are explained here:
peterlaursen
Participantbug confirmed! (latest interanl 5.1 build, MySQL 5.0.45)
very easy to see if you disable 'word wrap' in the editor where you view it!
and BTW: compliments for an excellent bug report!
peterlaursen
Participantbtw.. you were posting in the MONyog category. Moving the post to SQLyog category!
peterlaursen
Participantyour request added here:
http://code.google.com/p/sqlyog/issues/detail?id=381
http://code.google.com/p/sqlyog/issues/detail?id=382
We should have 'select/deselect all' in ALL grids! We all agree!
What are the parameters that you want structure sync to remember (note that if you have a gmail address you can add yourself to the issue tracker)
-
AuthorPosts