Thread: [Codestriker-user] 1.9.2 Database Creation UTF8
Brought to you by:
sits
From: Tim C. <tim...@sh...> - 2006-07-20 13:51:53
|
I am having a problem with database creation in 1.9.2 on RHEL4 with MySQL 4.1.20. When I run install.pl I get the following error message: Checking for LWP::UserAgent (any) ok: found v2.031 Checking for CGI (v2.56) ok: found v3.05 Checking for Net::SMTP (any) ok: found v2.29 Checking for MIME::QuotedPrint (any) ok: found v3.07 Checking for DBI (v1.13) ok: found v1.40 Checking for Template (v2.07) ok: found v2.15 Checking for HTML::Entities (any) ok: found v1.27 Checking for File::Temp (any) ok: found v0.16 Checking for XML::RSS (v1.05) ok: found v1.10 Checking for Encode::Byte (any) ok: found v2.00 Checking for Encode::Unicode (any) ok: found v2.00 Checking for Authen::SASL (any) ok: found v2.10 Checking for DBD::mysql (any) ok: found v2.9004 Creating table topicusermetric... DBD::mysql::db do failed: Specified key was too long; max key length is 1000 bytes at ../lib/Codestriker/DB/Database.pm line 137. Unable to create table/indexes. Three tables get created successfully. mysql> show tables; +--------------------------+ | Tables_in_codestrikerdb2 | +--------------------------+ | topic | | topichistory | | topicviewhistory | +--------------------------+ 3 rows in set (0.00 sec) Any ideas? Thanks, -- Tim Casada |
From: Vladimir S. <vsi...@gm...> - 2006-07-20 16:39:50
|
Hi Tim, I meant to submit this problem as well. I see it on Fedora Core 5. The workaround for me is rather simple. I replace email field length from 255 to 100 (if I remember it correctly, there are 3 places in install.pl where it should be done). After that, everything works fine. Thanks, --Vladimir On 7/20/06, Tim Casada <tim...@sh...> wrote: > I am having a problem with database creation in 1.9.2 on RHEL4 with > MySQL 4.1.20. When I run install.pl I get the following error message: > > Checking for LWP::UserAgent (any) ok: found v2.031 > Checking for CGI (v2.56) ok: found v3.05 > Checking for Net::SMTP (any) ok: found v2.29 > Checking for MIME::QuotedPrint (any) ok: found v3.07 > Checking for DBI (v1.13) ok: found v1.40 > Checking for Template (v2.07) ok: found v2.15 > Checking for HTML::Entities (any) ok: found v1.27 > Checking for File::Temp (any) ok: found v0.16 > Checking for XML::RSS (v1.05) ok: found v1.10 > Checking for Encode::Byte (any) ok: found v2.00 > Checking for Encode::Unicode (any) ok: found v2.00 > Checking for Authen::SASL (any) ok: found v2.10 > Checking for DBD::mysql (any) ok: found v2.9004 > Creating table topicusermetric... > DBD::mysql::db do failed: Specified key was too long; max key length is > 1000 bytes at ../lib/Codestriker/DB/Database.pm line 137. > Unable to create table/indexes. > > Three tables get created successfully. > > mysql> show tables; > +--------------------------+ > | Tables_in_codestrikerdb2 | > +--------------------------+ > | topic | > | topichistory | > | topicviewhistory | > +--------------------------+ > 3 rows in set (0.00 sec) > > > Any ideas? > > Thanks, > > -- > Tim Casada > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Codestriker-user mailing list > Cod...@li... > https://lists.sourceforge.net/lists/listinfo/codestriker-user > |
From: David S. <si...@us...> - 2006-07-21 02:33:55
|
Well, isn't that interesting? Since moving to UTF8, worst case is 4 bytes per character, so now for varchar fields of length 255, MySQL probably reserves 255 * 4 bytes for it, which is now above this 1000 pk byte limit I have never heard of! I have been using MySQL 5.1, so I haven't seen this issue. This must be a limitation of earlier releases. Anyway - I'll make some changes so we can get this working. Bit of a pain alright, but changing the length of the fields to 100 is a reasonable workaround. I wouldn't expect any email addresses longer than that anyway. Cheers, David Vladimir Sizikov wrote: > Hi Tim, > > I meant to submit this problem as well. I see it on Fedora Core 5. > The workaround for me is rather simple. I replace email field length > from 255 to 100 (if I remember it correctly, there are 3 places in > install.pl where it should be done). > > After that, everything works fine. > > Thanks, > --Vladimir > > On 7/20/06, Tim Casada <tim...@sh...> wrote: >> I am having a problem with database creation in 1.9.2 on RHEL4 with >> MySQL 4.1.20. When I run install.pl I get the following error message: >> >> Checking for LWP::UserAgent (any) ok: found v2.031 >> Checking for CGI (v2.56) ok: found v3.05 >> Checking for Net::SMTP (any) ok: found v2.29 >> Checking for MIME::QuotedPrint (any) ok: found v3.07 >> Checking for DBI (v1.13) ok: found v1.40 >> Checking for Template (v2.07) ok: found v2.15 >> Checking for HTML::Entities (any) ok: found v1.27 >> Checking for File::Temp (any) ok: found v0.16 >> Checking for XML::RSS (v1.05) ok: found v1.10 >> Checking for Encode::Byte (any) ok: found v2.00 >> Checking for Encode::Unicode (any) ok: found v2.00 >> Checking for Authen::SASL (any) ok: found v2.10 >> Checking for DBD::mysql (any) ok: found v2.9004 >> Creating table topicusermetric... >> DBD::mysql::db do failed: Specified key was too long; max key length is >> 1000 bytes at ../lib/Codestriker/DB/Database.pm line 137. >> Unable to create table/indexes. >> >> Three tables get created successfully. >> >> mysql> show tables; >> +--------------------------+ >> | Tables_in_codestrikerdb2 | >> +--------------------------+ >> | topic | >> | topichistory | >> | topicviewhistory | >> +--------------------------+ >> 3 rows in set (0.00 sec) >> >> >> Any ideas? >> >> Thanks, >> >> -- >> Tim Casada |
From: David S. <si...@us...> - 2006-07-21 04:38:54
|
Well, under Windoze, MySQL 4.1.20 and 5.1 work fine without any change to install.pl. Perhaps this is some specific issue with their Linux implementation. Cheers, David David Sitsky wrote: > Well, isn't that interesting? Since moving to UTF8, worst case is 4 > bytes per character, so now for varchar fields of length 255, MySQL > probably reserves 255 * 4 bytes for it, which is now above this 1000 pk > byte limit I have never heard of! > > I have been using MySQL 5.1, so I haven't seen this issue. This must be > a limitation of earlier releases. > > Anyway - I'll make some changes so we can get this working. Bit of a > pain alright, but changing the length of the fields to 100 is a > reasonable workaround. I wouldn't expect any email addresses longer > than that anyway. > > Cheers, > David > > Vladimir Sizikov wrote: >> Hi Tim, >> >> I meant to submit this problem as well. I see it on Fedora Core 5. >> The workaround for me is rather simple. I replace email field length >> from 255 to 100 (if I remember it correctly, there are 3 places in >> install.pl where it should be done). >> >> After that, everything works fine. >> >> Thanks, >> --Vladimir >> >> On 7/20/06, Tim Casada <tim...@sh...> wrote: >>> I am having a problem with database creation in 1.9.2 on RHEL4 with >>> MySQL 4.1.20. When I run install.pl I get the following error message: >>> >>> Checking for LWP::UserAgent (any) ok: found v2.031 >>> Checking for CGI (v2.56) ok: found v3.05 >>> Checking for Net::SMTP (any) ok: found v2.29 >>> Checking for MIME::QuotedPrint (any) ok: found v3.07 >>> Checking for DBI (v1.13) ok: found v1.40 >>> Checking for Template (v2.07) ok: found v2.15 >>> Checking for HTML::Entities (any) ok: found v1.27 >>> Checking for File::Temp (any) ok: found v0.16 >>> Checking for XML::RSS (v1.05) ok: found v1.10 >>> Checking for Encode::Byte (any) ok: found v2.00 >>> Checking for Encode::Unicode (any) ok: found v2.00 >>> Checking for Authen::SASL (any) ok: found v2.10 >>> Checking for DBD::mysql (any) ok: found v2.9004 >>> Creating table topicusermetric... >>> DBD::mysql::db do failed: Specified key was too long; max key length is >>> 1000 bytes at ../lib/Codestriker/DB/Database.pm line 137. >>> Unable to create table/indexes. >>> >>> Three tables get created successfully. >>> >>> mysql> show tables; >>> +--------------------------+ >>> | Tables_in_codestrikerdb2 | >>> +--------------------------+ >>> | topic | >>> | topichistory | >>> | topicviewhistory | >>> +--------------------------+ >>> 3 rows in set (0.00 sec) >>> >>> >>> Any ideas? >>> >>> Thanks, >>> >>> -- >>> Tim Casada > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Codestriker-user mailing list > Cod...@li... > https://lists.sourceforge.net/lists/listinfo/codestriker-user > |
From: David S. <si...@us...> - 2006-07-21 05:54:13
|
I just tried 4.1.20 under Linux with no problems as well! This is very strange, perhaps under RHEL4, they have configured MySQL in a different way which has this limitation. Cheers, David David Sitsky wrote: > Well, under Windoze, MySQL 4.1.20 and 5.1 work fine without any change > to install.pl. Perhaps this is some specific issue with their Linux > implementation. > > Cheers, > David > > David Sitsky wrote: >> Well, isn't that interesting? Since moving to UTF8, worst case is 4 >> bytes per character, so now for varchar fields of length 255, MySQL >> probably reserves 255 * 4 bytes for it, which is now above this 1000 pk >> byte limit I have never heard of! >> >> I have been using MySQL 5.1, so I haven't seen this issue. This must be >> a limitation of earlier releases. >> >> Anyway - I'll make some changes so we can get this working. Bit of a >> pain alright, but changing the length of the fields to 100 is a >> reasonable workaround. I wouldn't expect any email addresses longer >> than that anyway. >> >> Cheers, >> David >> >> Vladimir Sizikov wrote: >>> Hi Tim, >>> >>> I meant to submit this problem as well. I see it on Fedora Core 5. >>> The workaround for me is rather simple. I replace email field length >>> from 255 to 100 (if I remember it correctly, there are 3 places in >>> install.pl where it should be done). >>> >>> After that, everything works fine. >>> >>> Thanks, >>> --Vladimir >>> >>> On 7/20/06, Tim Casada <tim...@sh...> wrote: >>>> I am having a problem with database creation in 1.9.2 on RHEL4 with >>>> MySQL 4.1.20. When I run install.pl I get the following error message: >>>> >>>> Checking for LWP::UserAgent (any) ok: found v2.031 >>>> Checking for CGI (v2.56) ok: found v3.05 >>>> Checking for Net::SMTP (any) ok: found v2.29 >>>> Checking for MIME::QuotedPrint (any) ok: found v3.07 >>>> Checking for DBI (v1.13) ok: found v1.40 >>>> Checking for Template (v2.07) ok: found v2.15 >>>> Checking for HTML::Entities (any) ok: found v1.27 >>>> Checking for File::Temp (any) ok: found v0.16 >>>> Checking for XML::RSS (v1.05) ok: found v1.10 >>>> Checking for Encode::Byte (any) ok: found v2.00 >>>> Checking for Encode::Unicode (any) ok: found v2.00 >>>> Checking for Authen::SASL (any) ok: found v2.10 >>>> Checking for DBD::mysql (any) ok: found v2.9004 >>>> Creating table topicusermetric... >>>> DBD::mysql::db do failed: Specified key was too long; max key length is >>>> 1000 bytes at ../lib/Codestriker/DB/Database.pm line 137. >>>> Unable to create table/indexes. >>>> >>>> Three tables get created successfully. >>>> >>>> mysql> show tables; >>>> +--------------------------+ >>>> | Tables_in_codestrikerdb2 | >>>> +--------------------------+ >>>> | topic | >>>> | topichistory | >>>> | topicviewhistory | >>>> +--------------------------+ >>>> 3 rows in set (0.00 sec) >>>> >>>> >>>> Any ideas? >>>> >>>> Thanks, >>>> >>>> -- >>>> Tim Casada >> >> ------------------------------------------------------------------------- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to share your >> opinions on IT & business topics through brief surveys -- and earn cash >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >> _______________________________________________ >> Codestriker-user mailing list >> Cod...@li... >> https://lists.sourceforge.net/lists/listinfo/codestriker-user >> > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Codestriker-user mailing list > Cod...@li... > https://lists.sourceforge.net/lists/listinfo/codestriker-user > |
From: David S. <si...@us...> - 2006-07-21 06:34:36
Attachments:
zot.txt
|
Ok, I managed to reproduce this under Linux after all. I have modified all the email fields in install.pl to be length 200, and this fixes the issue. I have uploaded 1.9.2rc3 to SF. I have also attached the patch to install.pl to this email if you just want to apply that (after zapping your codestrikerdb database). I'll actually be away from email for the next two weeks on holidays, but Jason will be able to help you out if you still have issues. Thanks for the report. Cheers, David |