Thread: [ postfixadmin-Bugs-1828857 ] mysql create database broken
Brought to you by:
christian_boltz,
gingerdog
Menu
▾
▴
postfixadmin-tracker
|
From: SourceForge.net <no...@so...> - 2007-11-09 10:00:31
|
Bugs item #1828857, was opened at 2007-11-09 02:00 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1828857&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Database Group: SVN (please specify revision!) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: mysql create database broken Initial Comment: >mysql -u root -p < DATABASE_MYSQL.TXT Enter password: ERROR 1071 (42000) at line 144: Specified key was too long; max key length is 1024 bytes Using svn revision 204, debian sarge, mysql4-1.11a from sarge backports changing the DATABASE_MYSQL.txt file to: -- CREATE TABLE vacation_notification ( on_vacation varchar(170) NOT NULL, notified varchar(170) NOT NULL, -- fixed the problem for me tho. Dunno if it is a mysql bug or not. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1828857&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2007-11-17 21:29:08
|
Bugs item #1828857, was opened at 2007-11-09 11:00 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1828857&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Database Group: SVN (please specify revision!) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: mysql create database broken Initial Comment: >mysql -u root -p < DATABASE_MYSQL.TXT Enter password: ERROR 1071 (42000) at line 144: Specified key was too long; max key length is 1024 bytes Using svn revision 204, debian sarge, mysql4-1.11a from sarge backports changing the DATABASE_MYSQL.txt file to: -- CREATE TABLE vacation_notification ( on_vacation varchar(170) NOT NULL, notified varchar(170) NOT NULL, -- fixed the problem for me tho. Dunno if it is a mysql bug or not. ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2007-11-17 22:29 Message: Logged In: YES user_id=593261 Originator: NO Looks like an utf8 problem... The key uses two varchar(255) field, which means the key is 2 * 255 chars long. And utf8 means 3 bytes per char, which results in 1530 bytes. Since these fields only contain mail addresses, I'll change them to latin1 encoding. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1828857&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2007-11-18 01:44:13
|
Bugs item #1828857, was opened at 2007-11-09 11:00 Message generated for change (Comment added) made by xpunkt You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1828857&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Database Group: SVN (please specify revision!) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: mysql create database broken Initial Comment: >mysql -u root -p < DATABASE_MYSQL.TXT Enter password: ERROR 1071 (42000) at line 144: Specified key was too long; max key length is 1024 bytes Using svn revision 204, debian sarge, mysql4-1.11a from sarge backports changing the DATABASE_MYSQL.txt file to: -- CREATE TABLE vacation_notification ( on_vacation varchar(170) NOT NULL, notified varchar(170) NOT NULL, -- fixed the problem for me tho. Dunno if it is a mysql bug or not. ---------------------------------------------------------------------- Comment By: Benny Pedersen (xpunkt) Date: 2007-11-18 02:44 Message: Logged In: YES user_id=774995 Originator: NO problem will then be that we loose utf8 encoded email handle, is this problem olso with postgresql and unicode ? i prefer unicode over latin-1 ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2007-11-17 22:29 Message: Logged In: YES user_id=593261 Originator: NO Looks like an utf8 problem... The key uses two varchar(255) field, which means the key is 2 * 255 chars long. And utf8 means 3 bytes per char, which results in 1530 bytes. Since these fields only contain mail addresses, I'll change them to latin1 encoding. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1828857&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2007-11-18 01:49:02
|
Bugs item #1828857, was opened at 2007-11-09 11:00 Message generated for change (Comment added) made by xpunkt You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1828857&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Database Group: SVN (please specify revision!) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: mysql create database broken Initial Comment: >mysql -u root -p < DATABASE_MYSQL.TXT Enter password: ERROR 1071 (42000) at line 144: Specified key was too long; max key length is 1024 bytes Using svn revision 204, debian sarge, mysql4-1.11a from sarge backports changing the DATABASE_MYSQL.txt file to: -- CREATE TABLE vacation_notification ( on_vacation varchar(170) NOT NULL, notified varchar(170) NOT NULL, -- fixed the problem for me tho. Dunno if it is a mysql bug or not. ---------------------------------------------------------------------- Comment By: Benny Pedersen (xpunkt) Date: 2007-11-18 02:49 Message: Logged In: YES user_id=774995 Originator: NO and the vacation.pl is utf8 so we have to find a better way ---------------------------------------------------------------------- Comment By: Benny Pedersen (xpunkt) Date: 2007-11-18 02:44 Message: Logged In: YES user_id=774995 Originator: NO problem will then be that we loose utf8 encoded email handle, is this problem olso with postgresql and unicode ? i prefer unicode over latin-1 ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2007-11-17 22:29 Message: Logged In: YES user_id=593261 Originator: NO Looks like an utf8 problem... The key uses two varchar(255) field, which means the key is 2 * 255 chars long. And utf8 means 3 bytes per char, which results in 1530 bytes. Since these fields only contain mail addresses, I'll change them to latin1 encoding. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1828857&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2007-11-18 14:13:16
|
Bugs item #1828857, was opened at 2007-11-09 11:00 Message generated for change (Comment added) made by amsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1828857&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Database Group: SVN (please specify revision!) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: mysql create database broken Initial Comment: >mysql -u root -p < DATABASE_MYSQL.TXT Enter password: ERROR 1071 (42000) at line 144: Specified key was too long; max key length is 1024 bytes Using svn revision 204, debian sarge, mysql4-1.11a from sarge backports changing the DATABASE_MYSQL.txt file to: -- CREATE TABLE vacation_notification ( on_vacation varchar(170) NOT NULL, notified varchar(170) NOT NULL, -- fixed the problem for me tho. Dunno if it is a mysql bug or not. ---------------------------------------------------------------------- Comment By: amsys (amsys) Date: 2007-11-18 15:13 Message: Logged In: YES user_id=1299438 Originator: NO I have already tried to solve this, but the problem is someone want's to make unicode domains in future, adresses as standart (probably someone very crazy, like bunch of managers) a) make collation latin1 general b) store used emails as hash in vacation table (shortens key) I've placed this long time ago, but it's probably outdated now?: http://sourceforge.net/tracker/index.php?func=detail&aid=1801073&group_id=191583&atid=937966 ---------------------------------------------------------------------- Comment By: Benny Pedersen (xpunkt) Date: 2007-11-18 02:49 Message: Logged In: YES user_id=774995 Originator: NO and the vacation.pl is utf8 so we have to find a better way ---------------------------------------------------------------------- Comment By: Benny Pedersen (xpunkt) Date: 2007-11-18 02:44 Message: Logged In: YES user_id=774995 Originator: NO problem will then be that we loose utf8 encoded email handle, is this problem olso with postgresql and unicode ? i prefer unicode over latin-1 ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2007-11-17 22:29 Message: Logged In: YES user_id=593261 Originator: NO Looks like an utf8 problem... The key uses two varchar(255) field, which means the key is 2 * 255 chars long. And utf8 means 3 bytes per char, which results in 1530 bytes. Since these fields only contain mail addresses, I'll change them to latin1 encoding. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1828857&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2007-11-18 19:19:14
|
Bugs item #1828857, was opened at 2007-11-09 11:00 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1828857&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Database Group: SVN (please specify revision!) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: mysql create database broken Initial Comment: >mysql -u root -p < DATABASE_MYSQL.TXT Enter password: ERROR 1071 (42000) at line 144: Specified key was too long; max key length is 1024 bytes Using svn revision 204, debian sarge, mysql4-1.11a from sarge backports changing the DATABASE_MYSQL.txt file to: -- CREATE TABLE vacation_notification ( on_vacation varchar(170) NOT NULL, notified varchar(170) NOT NULL, -- fixed the problem for me tho. Dunno if it is a mysql bug or not. ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2007-11-18 20:19 Message: Logged In: YES user_id=593261 Originator: NO unicode domains are always "punicode"-encoded, for example "blöd.de" is encoded as "xn--bld-tna.de". Does anyone see non-ASCII characters? ;-) See https://sourceforge.net/forum/message.php?msg_id=4572821 for more details. ---------------------------------------------------------------------- Comment By: amsys (amsys) Date: 2007-11-18 15:13 Message: Logged In: YES user_id=1299438 Originator: NO I have already tried to solve this, but the problem is someone want's to make unicode domains in future, adresses as standart (probably someone very crazy, like bunch of managers) a) make collation latin1 general b) store used emails as hash in vacation table (shortens key) I've placed this long time ago, but it's probably outdated now?: http://sourceforge.net/tracker/index.php?func=detail&aid=1801073&group_id=191583&atid=937966 ---------------------------------------------------------------------- Comment By: Benny Pedersen (xpunkt) Date: 2007-11-18 02:49 Message: Logged In: YES user_id=774995 Originator: NO and the vacation.pl is utf8 so we have to find a better way ---------------------------------------------------------------------- Comment By: Benny Pedersen (xpunkt) Date: 2007-11-18 02:44 Message: Logged In: YES user_id=774995 Originator: NO problem will then be that we loose utf8 encoded email handle, is this problem olso with postgresql and unicode ? i prefer unicode over latin-1 ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2007-11-17 22:29 Message: Logged In: YES user_id=593261 Originator: NO Looks like an utf8 problem... The key uses two varchar(255) field, which means the key is 2 * 255 chars long. And utf8 means 3 bytes per char, which results in 1530 bytes. Since these fields only contain mail addresses, I'll change them to latin1 encoding. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1828857&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-01-03 15:03:58
|
Bugs item #1828857, was opened at 2007-11-09 12:00 Message generated for change (Comment added) made by goshoo You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1828857&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Database Group: SVN (please specify revision!) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: mysql create database broken Initial Comment: >mysql -u root -p < DATABASE_MYSQL.TXT Enter password: ERROR 1071 (42000) at line 144: Specified key was too long; max key length is 1024 bytes Using svn revision 204, debian sarge, mysql4-1.11a from sarge backports changing the DATABASE_MYSQL.txt file to: -- CREATE TABLE vacation_notification ( on_vacation varchar(170) NOT NULL, notified varchar(170) NOT NULL, -- fixed the problem for me tho. Dunno if it is a mysql bug or not. ---------------------------------------------------------------------- Comment By: Georgi Naplatanov (goshoo) Date: 2008-01-03 17:04 Message: Logged In: YES user_id=181398 Originator: NO > problem will then be that we loose utf8 encoded email handle, is this > problem olso with postgresql and unicode ? Not really, it's a mysql bug - see http://bugs.mysql.com/bug.php?id=4541 UTF-8 has a variable lenght ( between 1 and 3 bytes per character), mysql allocates maximum space. ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2007-11-18 21:19 Message: Logged In: YES user_id=593261 Originator: NO unicode domains are always "punicode"-encoded, for example "blöd.de" is encoded as "xn--bld-tna.de". Does anyone see non-ASCII characters? ;-) See https://sourceforge.net/forum/message.php?msg_id=4572821 for more details. ---------------------------------------------------------------------- Comment By: amsys (amsys) Date: 2007-11-18 16:13 Message: Logged In: YES user_id=1299438 Originator: NO I have already tried to solve this, but the problem is someone want's to make unicode domains in future, adresses as standart (probably someone very crazy, like bunch of managers) a) make collation latin1 general b) store used emails as hash in vacation table (shortens key) I've placed this long time ago, but it's probably outdated now?: http://sourceforge.net/tracker/index.php?func=detail&aid=1801073&group_id=191583&atid=937966 ---------------------------------------------------------------------- Comment By: Benny Pedersen (xpunkt) Date: 2007-11-18 03:49 Message: Logged In: YES user_id=774995 Originator: NO and the vacation.pl is utf8 so we have to find a better way ---------------------------------------------------------------------- Comment By: Benny Pedersen (xpunkt) Date: 2007-11-18 03:44 Message: Logged In: YES user_id=774995 Originator: NO problem will then be that we loose utf8 encoded email handle, is this problem olso with postgresql and unicode ? i prefer unicode over latin-1 ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2007-11-17 23:29 Message: Logged In: YES user_id=593261 Originator: NO Looks like an utf8 problem... The key uses two varchar(255) field, which means the key is 2 * 255 chars long. And utf8 means 3 bytes per char, which results in 1530 bytes. Since these fields only contain mail addresses, I'll change them to latin1 encoding. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1828857&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-03-04 23:51:53
|
Bugs item #1828857, was opened at 2007-11-09 11:00 Message generated for change (Settings changed) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1828857&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Database Group: SVN (please specify revision!) Status: Open Resolution: None >Priority: 9 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: mysql create database broken Initial Comment: >mysql -u root -p < DATABASE_MYSQL.TXT Enter password: ERROR 1071 (42000) at line 144: Specified key was too long; max key length is 1024 bytes Using svn revision 204, debian sarge, mysql4-1.11a from sarge backports changing the DATABASE_MYSQL.txt file to: -- CREATE TABLE vacation_notification ( on_vacation varchar(170) NOT NULL, notified varchar(170) NOT NULL, -- fixed the problem for me tho. Dunno if it is a mysql bug or not. ---------------------------------------------------------------------- Comment By: Georgi Naplatanov (goshoo) Date: 2008-01-03 16:04 Message: Logged In: YES user_id=181398 Originator: NO > problem will then be that we loose utf8 encoded email handle, is this > problem olso with postgresql and unicode ? Not really, it's a mysql bug - see http://bugs.mysql.com/bug.php?id=4541 UTF-8 has a variable lenght ( between 1 and 3 bytes per character), mysql allocates maximum space. ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2007-11-18 20:19 Message: Logged In: YES user_id=593261 Originator: NO unicode domains are always "punicode"-encoded, for example "blöd.de" is encoded as "xn--bld-tna.de". Does anyone see non-ASCII characters? ;-) See https://sourceforge.net/forum/message.php?msg_id=4572821 for more details. ---------------------------------------------------------------------- Comment By: amsys (amsys) Date: 2007-11-18 15:13 Message: Logged In: YES user_id=1299438 Originator: NO I have already tried to solve this, but the problem is someone want's to make unicode domains in future, adresses as standart (probably someone very crazy, like bunch of managers) a) make collation latin1 general b) store used emails as hash in vacation table (shortens key) I've placed this long time ago, but it's probably outdated now?: http://sourceforge.net/tracker/index.php?func=detail&aid=1801073&group_id=191583&atid=937966 ---------------------------------------------------------------------- Comment By: Benny Pedersen (xpunkt) Date: 2007-11-18 02:49 Message: Logged In: YES user_id=774995 Originator: NO and the vacation.pl is utf8 so we have to find a better way ---------------------------------------------------------------------- Comment By: Benny Pedersen (xpunkt) Date: 2007-11-18 02:44 Message: Logged In: YES user_id=774995 Originator: NO problem will then be that we loose utf8 encoded email handle, is this problem olso with postgresql and unicode ? i prefer unicode over latin-1 ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2007-11-17 22:29 Message: Logged In: YES user_id=593261 Originator: NO Looks like an utf8 problem... The key uses two varchar(255) field, which means the key is 2 * 255 chars long. And utf8 means 3 bytes per char, which results in 1530 bytes. Since these fields only contain mail addresses, I'll change them to latin1 encoding. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1828857&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-04-06 23:30:34
|
Bugs item #1828857, was opened at 2007-11-09 11:00 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1828857&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Database Group: SVN (please specify revision!) Status: Open Resolution: None Priority: 9 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: mysql create database broken Initial Comment: >mysql -u root -p < DATABASE_MYSQL.TXT Enter password: ERROR 1071 (42000) at line 144: Specified key was too long; max key length is 1024 bytes Using svn revision 204, debian sarge, mysql4-1.11a from sarge backports changing the DATABASE_MYSQL.txt file to: -- CREATE TABLE vacation_notification ( on_vacation varchar(170) NOT NULL, notified varchar(170) NOT NULL, -- fixed the problem for me tho. Dunno if it is a mysql bug or not. ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2008-04-07 01:30 Message: Logged In: YES user_id=593261 Originator: NO This should be fixed in the latest SVN version (r319). Can you please test it by running upgrade.php? Note: I can't guarantee a clean update. If something goes wrong (you'll see an "Invalid query" message in this case), please drop the table vacation_notification (it contains a list of mail adresses who have received vacation notifications already, so the worst thing that might happen is that some of them receive another one when sending the next mail). ---------------------------------------------------------------------- Comment By: Georgi Naplatanov (goshoo) Date: 2008-01-03 16:04 Message: Logged In: YES user_id=181398 Originator: NO > problem will then be that we loose utf8 encoded email handle, is this > problem olso with postgresql and unicode ? Not really, it's a mysql bug - see http://bugs.mysql.com/bug.php?id=4541 UTF-8 has a variable lenght ( between 1 and 3 bytes per character), mysql allocates maximum space. ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2007-11-18 20:19 Message: Logged In: YES user_id=593261 Originator: NO unicode domains are always "punicode"-encoded, for example "blöd.de" is encoded as "xn--bld-tna.de". Does anyone see non-ASCII characters? ;-) See https://sourceforge.net/forum/message.php?msg_id=4572821 for more details. ---------------------------------------------------------------------- Comment By: amsys (amsys) Date: 2007-11-18 15:13 Message: Logged In: YES user_id=1299438 Originator: NO I have already tried to solve this, but the problem is someone want's to make unicode domains in future, adresses as standart (probably someone very crazy, like bunch of managers) a) make collation latin1 general b) store used emails as hash in vacation table (shortens key) I've placed this long time ago, but it's probably outdated now?: http://sourceforge.net/tracker/index.php?func=detail&aid=1801073&group_id=191583&atid=937966 ---------------------------------------------------------------------- Comment By: Benny Pedersen (xpunkt) Date: 2007-11-18 02:49 Message: Logged In: YES user_id=774995 Originator: NO and the vacation.pl is utf8 so we have to find a better way ---------------------------------------------------------------------- Comment By: Benny Pedersen (xpunkt) Date: 2007-11-18 02:44 Message: Logged In: YES user_id=774995 Originator: NO problem will then be that we loose utf8 encoded email handle, is this problem olso with postgresql and unicode ? i prefer unicode over latin-1 ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2007-11-17 22:29 Message: Logged In: YES user_id=593261 Originator: NO Looks like an utf8 problem... The key uses two varchar(255) field, which means the key is 2 * 255 chars long. And utf8 means 3 bytes per char, which results in 1530 bytes. Since these fields only contain mail addresses, I'll change them to latin1 encoding. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1828857&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-04-25 22:58:46
|
Bugs item #1828857, was opened at 2007-11-09 11:00 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1828857&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Database Group: SVN (please specify revision!) >Status: Closed >Resolution: Fixed Priority: 9 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: mysql create database broken Initial Comment: >mysql -u root -p < DATABASE_MYSQL.TXT Enter password: ERROR 1071 (42000) at line 144: Specified key was too long; max key length is 1024 bytes Using svn revision 204, debian sarge, mysql4-1.11a from sarge backports changing the DATABASE_MYSQL.txt file to: -- CREATE TABLE vacation_notification ( on_vacation varchar(170) NOT NULL, notified varchar(170) NOT NULL, -- fixed the problem for me tho. Dunno if it is a mysql bug or not. ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2008-04-26 00:58 Message: Logged In: YES user_id=593261 Originator: NO I just verified that this is fixed by creating a new database using SVN r343. ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2008-04-07 01:30 Message: Logged In: YES user_id=593261 Originator: NO This should be fixed in the latest SVN version (r319). Can you please test it by running upgrade.php? Note: I can't guarantee a clean update. If something goes wrong (you'll see an "Invalid query" message in this case), please drop the table vacation_notification (it contains a list of mail adresses who have received vacation notifications already, so the worst thing that might happen is that some of them receive another one when sending the next mail). ---------------------------------------------------------------------- Comment By: Georgi Naplatanov (goshoo) Date: 2008-01-03 16:04 Message: Logged In: YES user_id=181398 Originator: NO > problem will then be that we loose utf8 encoded email handle, is this > problem olso with postgresql and unicode ? Not really, it's a mysql bug - see http://bugs.mysql.com/bug.php?id=4541 UTF-8 has a variable lenght ( between 1 and 3 bytes per character), mysql allocates maximum space. ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2007-11-18 20:19 Message: Logged In: YES user_id=593261 Originator: NO unicode domains are always "punicode"-encoded, for example "blöd.de" is encoded as "xn--bld-tna.de". Does anyone see non-ASCII characters? ;-) See https://sourceforge.net/forum/message.php?msg_id=4572821 for more details. ---------------------------------------------------------------------- Comment By: amsys (amsys) Date: 2007-11-18 15:13 Message: Logged In: YES user_id=1299438 Originator: NO I have already tried to solve this, but the problem is someone want's to make unicode domains in future, adresses as standart (probably someone very crazy, like bunch of managers) a) make collation latin1 general b) store used emails as hash in vacation table (shortens key) I've placed this long time ago, but it's probably outdated now?: http://sourceforge.net/tracker/index.php?func=detail&aid=1801073&group_id=191583&atid=937966 ---------------------------------------------------------------------- Comment By: Benny Pedersen (xpunkt) Date: 2007-11-18 02:49 Message: Logged In: YES user_id=774995 Originator: NO and the vacation.pl is utf8 so we have to find a better way ---------------------------------------------------------------------- Comment By: Benny Pedersen (xpunkt) Date: 2007-11-18 02:44 Message: Logged In: YES user_id=774995 Originator: NO problem will then be that we loose utf8 encoded email handle, is this problem olso with postgresql and unicode ? i prefer unicode over latin-1 ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2007-11-17 22:29 Message: Logged In: YES user_id=593261 Originator: NO Looks like an utf8 problem... The key uses two varchar(255) field, which means the key is 2 * 255 chars long. And utf8 means 3 bytes per char, which results in 1530 bytes. Since these fields only contain mail addresses, I'll change them to latin1 encoding. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1828857&group_id=191583 |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X