Importing Invite database

[void4ever]

Hey there guys, so i'm having some trouble importing the invite sql statements to a linux box running Mysql v4.0.26

here is the error log

Query:
CREATE TABLE `invite_hosts` (
`ftp_user` varchar(255) NOT NULL default '',
`hostmask` varchar(255) NOT NULL default '',
PRIMARY KEY (`ftp_user`,`hostmask`)
)

Error occured at:2005-12-22 15:06:42
Line no.:18
Error Code: 1071 - Specified key was too long. Max key length is 500

unfortunatly i don't know jack about sql so i'm not sure how to rewrite this to fix it. I'm using the invite.sql file included with 0.6.0. And i know i got this to import once before on it's windows counterpart, same version.

Any ideas?

Void4ever

[Harm]

You could try to use shorter varchar fields. If the maximum length of the key is 500 in this version of mysql, using VARCHAR(250) for each field should be ok.

Note that I have no idea how this invite script works. This small change shouldn't break anything but it might..

[void4ever]

I might try that, but whats odd is the user part of the database is importing just fine.

CREATE TABLE `invite_users` (
`ftp_user` varchar(255) NOT NULL default '', -- FTP user name.
`irc_user` varchar(255) default NULL, -- IRC user name.
`online` tinyint(1) NOT NULL default '0', -- Indicates if the user is on IRC.
`password` varchar(255) default NULL, -- Password hash (PKCS #5 v2 based).
`time` int(10) NOT NULL default '0', -- Time stamp of last activity.
PRIMARY KEY (`ftp_user`)
);

CREATE TABLE `invite_hosts` (
`ftp_user` varchar(255) NOT NULL default '', -- FTP user name.
`hostmask` varchar(255) NOT NULL default '', -- IRC host mask (ident@host).
PRIMARY KEY (`ftp_user`,`hostmask`)
);

As you can see the invite user table is using a 255 var as well. And i got no complaints from the server on that first part. And the other thing is if i remember i had the exact same version on my windows box (wanted to test the version to make sure it was compatible) and it worked just fine. Of course were talking different platforms here windows and linux, but that normally shouldn't affect a GOOD port.

Void4ever

[Harm]

CREATE TABLE `invite_users` (
`ftp_user` varchar(255) NOT NULL default '', -- FTP user name.
`irc_user` varchar(255) default NULL, -- IRC user name.
`online` tinyint(1) NOT NULL default '0', -- Indicates if the user is on IRC.
`password` varchar(255) default NULL, -- Password hash (PKCS #5 v2 based).
`time` int(10) NOT NULL default '0', -- Time stamp of last activity.
PRIMARY KEY (`ftp_user`)
);

In this case, the key is based on the ftp_user field and thus the key is 255 chars long.

CREATE TABLE `invite_hosts` (
`ftp_user` varchar(255) NOT NULL default '', -- FTP user name.
`hostmask` varchar(255) NOT NULL default '', -- IRC host mask (ident@host).
PRIMARY KEY (`ftp_user`,`hostmask`)
);

In this case, the key is based on both the ftp_user and the hostmask fields and thus it's 2 * 255 = 510 chars long. It looks like this version of mysql can't handle more than 500 chars for the key.

If you're sure both versions are identical, it might be something else like an ini setting. I'm afraid I can't help you much with the mysql daemon configuration. I'm using databases, I'm not administrating them.

[neoxed]

I've only tested it with MySQL v5.0, not sure how well it works with v4.0, or even v4.1 for that matter. Perhaps in v5.0 the length restriction was removed.

[void4ever]

well i've done a bit of coding in my time so as far as i see it, there shouldn't be any issues reducing the var length then correct? As long as i'm not using a hostname name 200 some odd chars correct?

I appreciate the info guys!!!

Void4ever