Yes, set the primary key to include both id and searchstring CREATE TABLE `test`. `new table` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `searchstring` varchar(45) NOT NULL, `count` int(10) unsigned NOT NULL, `timest` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, PRIMARY KEY (`id`,`searchstring`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1 You can change the existing table using: ALTER TABLE `test`. `new table` DROP PRIMARY KEY, ADD PRIMARY KEY USING BTREE(`id`) ADD UNIQUE INDEX ss(searchstring).
Yes, set the primary key to include both id and searchstring CREATE TABLE `test`. `new table` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `searchstring` varchar(45) NOT NULL, `count` int(10) unsigned NOT NULL, `timest` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, PRIMARY KEY (`id`,`searchstring`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1; You can change the existing table using: ALTER TABLE `test`. `new table` DROP PRIMARY KEY, ADD PRIMARY KEY USING BTREE(`id`) ADD UNIQUE INDEX ss(searchstring).
– Michael May 21 at 23:18 The alter worked! – Michael May 22 at 17:36 This suggestion alters the table to allow duplicate IDs and duplicate searchstrings - not what was asked for. A better answer would be to make both columns unique, not create a compound key.
– dportas May 23 at 12:52 @dportas, fixed now. – Johan May 23 at 22:03.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.