Forum Replies Created
-
AuthorPosts
-
peterlaursen
ParticipantBoth of those:
1) grouping and filtering connections
2) multiple connections in one connections windows
.. are existing requests
1) is much more simple than 2) to implement. But with 2) drag'n'drop for copying between servers could be enabled.
Realistically it will take at least 4 months before any such GUI 'revamp' can be considered.
peterlaursen
Participantonly it should be
Code:drop table if exists sometable;peterlaursen
Participanttry
SELECT
`clienthistoryaction`.`Employe_ID`,
`clienthistoryaction`.`Client_ID`,
if((action_id=1),count(action_id),0) as action_1_count,
if((action_id=2),count(action_id),0) as action_2_count,
if((action_id=3),count(action_id),0) as action_3_count
FROM
`clienthistoryaction`
GROUP BY `clienthistoryaction`.`Employe_ID`,`clienthistoryaction`.`Client_ID`,`clienthistoryaction`.`Action_ID`;
and
SELECT
`clienthistoryaction`.`Employe_ID`,
`clienthistoryaction`.`Client_ID`,
if((action_id=1),count(action_id),0) as action_1_count,
if((action_id=2),count(action_id),0) as action_2_count,
if((action_id=3),count(action_id),0) as action_3_count,
`actionregistry`.`ActionName`
FROM
`clienthistoryaction`
INNER JOIN `actionregistry` ON (`clienthistoryaction`.`Action_ID` = `actionregistry`.`ID`)
GROUP BY `clienthistoryaction`.`Employe_ID`,`clienthistoryaction`.`Client_ID`,action_id;
If you want to substitute the string 'action_1_count' with the value “Phone call” etc in the header you need to use 'prepared statements' to generate such alias!
and you may of course too
drop table sometable if exists; — drop any old table
create table sometable as — populate table with query result
SELECT
`clienthistoryaction`.`Employe_ID`,
`clienthistoryaction`.`Client_ID`,
if((action_id=1),count(action_id),0) as action_1_count,
if((action_id=2),count(action_id),0) as action_2_count,
if((action_id=3),count(action_id),0) as action_3_count
FROM
`clienthistoryaction`
GROUP BY `clienthistoryaction`.`Employe_ID`,`clienthistoryaction`.`Client_ID`,`clienthistoryaction`.`Action_ID`;
alter table `sometable` add column `id` int NOT NULL AUTO_INCREMENT first, add primary key(`id`); — add an autoincrement primary key
peterlaursen
ParticipantNobody can help as long it is not clear exactly what you want to do! Too many words and too little exact information here!
You will have to create a test/demo case with
* two small tables and a few rows of data in each only (two small dumps).
* a table view of what result should be with this example.
peterlaursen
Participant“The only way is restarting the Pc. This is not the first time that i got that Crash.” .. yes .. and i wish we could do anything about it! It is a Vista issue, basically, I believe.
We have not had such reports wiht recent versions and an updated Vista (I think it is more than 6 months since we had last time). Do you have Vista SP1 intalled? Please first upgrade SQLyog to 7.11 or 7.12 RC and ensure that your OS is updated. We cannot do anything with problems related to old versions like 6.06 anyway.
Please create a support ticket if you want us to discuss upgrade with us.
peterlaursen
ParticipantThere is an option to refresh the Object Browser (the 'recycle' icon). It will refresh the currently selected node. To refresh the tables-list select the database and refresh. Doesn't this work?
peterlaursen
ParticipantPlease create the ticket from this link:
http://www.webyog.com/support/ttx.cgi
You will have to do because else you cannot follow discussion there!
peterlaursen
ParticipantThe problem msut be related to the communication of the 'user profile' between domain server and your local. But if it is not autocomplete thne it can only be the .ini file and that should not take that much time!
We will discuss this!
peterlaursen
ParticipantStrange .. i can create the table, drop the Pk, drop the table and create the table again.
As you are using InnoDB I might think is is related to transactions that were not commited!
Have you started a transaction from the editor?
Does SHOW TABLES tell that table is still there?
peterlaursen
ParticipantIn your case you are not wrong. But other users may work on a database that is 'live'.
peterlaursen
ParticipantThe problem is that it is not without risk to change (engine, index. charset) 'silently'. At least we should prompt user for accept! And there will be more options to solve this and only user can make the decision about what he wants.
The may be *lots* of client programs using the database simutaneously. That is an important difference between a database server and personal/office databases like Access. One client cannot act on it own without risk for others. For instance building an index on a huge table may result in LOCKs making the database unavailable for other clients. An (admin) user will have to take decision about *what* and *when* to do. Anything else would be gambling!
But true that we could do some client side validation, that would make the problem easier understandable than what the (here rather meaningless) server error message does. But still basically the problem with hopeless MySQL error messages should be solved server-side.
peterlaursen
ParticipantI have already add to our issue tracker
peterlaursen
Participant@mahesh .. I think no need for the crash dump here? This is a known issue already! Any particular reason why you want it?
peterlaursen
ParticipantWith all columns involved in FK's as UTF8 the FK creates:
[attachment=1011:before.jpg] [attachment=1012:after.jpg]
peterlaursen
ParticipantI think Mahesh misunderstood
Execute
CREATE TABLE `pllanguages` (
`Language-id` smallint(5) NOT NULL,
PRIMARY KEY (`Language-id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8
PLtext CREATE TABLE `PLtext` (
`text-id` smallint(5) unsigned NOT NULL auto_increment,
`textlocation` varchar(20) NOT NULL,
`textfield` text,
PRIMARY KEY (`text-id`),
UNIQUE KEY `NewIndex1` (`textlocation`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 CHECKSUM=1 DELAY_KEY_WRITE=1 ROW_FORMAT=DYNAMIC
CREATE TABLE `PLtextlocation` (
`textlocation` varchar(20) NOT NULL,
`Language-id` smallint(5) NOT NULL,
PRIMARY KEY (`textlocation`),
UNIQUE KEY `NewIndex2` (`Language-id`),
CONSTRAINT `FK_PLtextlocation` FOREIGN KEY (`Language-id`) REFERENCES `PLLanguages` (`Language-id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1
And you are right it will not create! But the problem here is that Foreign Keys cannot be established of columns wiht different charsets (and not even different collations!)! One of your examples is utf8 another is latin 1! Make charset the same and it will work!
Additional comments:
“f the tables are not the right kind? PLEASE, do MAKE them so without me knowing it, and is there no index? PLEASE create one, without me knowing it.”
I think not really possible!
1) True that currently the most significant ENGINE supporting FK's is INNODB but it is not the only one. You may say that SolidDB and PBXT are exotic, but FALCON is also planned to support in future.
2) Only user can decide if the key shall be unique or not and if it shall span one or more columns.
But we could do some more client side validation before sending to the serverin order to produce better error messages!
-
AuthorPosts