Hi,
I am having trouble creating the xcap_xml table of the new presence module in mysql (latest 4.1.22 on RHEL 4).
The table definition from the docs is:
CREATE TABLE `xcap_xml` ( `user` varchar(256) NOT NULL, `domain` varchar(256) NOT NULL, `xcap` text NOT NULL, `doc_type` varchar(64) NOT NULL, PRIMARY KEY (`user`,`domain`,`doc_type`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1;
I get the following error: ERROR 1170 (42000): BLOB/TEXT column 'user' used in key specification without a key length
In my opinion, the problem is the definition of the user and domain columns, which are varchar(256), instead of varchar(255) and are automatically promoted to text columns. If changing the size to 255, everything is fine.
Does the presence db code do some length checks that can be affected by this change? Is the table definition correct or am I missing something?
Thanks, Cristian
Hello,
the size of those columns was adjusted to match other tables -- it was a mistake in the documentation -- I have updated it: http://www.openser.org/docs/modules/1.2.x/presence.html#AEN199 http://openser.org/dokuwiki/doku.php/presence:database-tables
Thanks for reporting, Daniel
On 01/11/07 11:55, Cristian Caprar wrote:
Hi,
I am having trouble creating the xcap_xml table of the new presence module in mysql (latest 4.1.22 on RHEL 4).
The table definition from the docs is:
CREATE TABLE `xcap_xml` ( `user` varchar(256) NOT NULL, `domain` varchar(256) NOT NULL, `xcap` text NOT NULL, `doc_type` varchar(64) NOT NULL, PRIMARY KEY (`user`,`domain`,`doc_type`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1;
I get the following error: ERROR 1170 (42000): BLOB/TEXT column 'user' used in key specification without a key length
In my opinion, the problem is the definition of the user and domain columns, which are varchar(256), instead of varchar(255) and are automatically promoted to text columns. If changing the size to 255, everything is fine.
Does the presence db code do some length checks that can be affected by this change? Is the table definition correct or am I missing something?
Thanks, Cristian
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Sweet ... :)
Thanks and regards, Cristian
-----Original Message----- From: Daniel-Constantin Mierla [mailto:daniel@voice-system.ro] Sent: Thursday, January 11, 2007 12:11 PM To: Cristian Caprar Cc: users@openser.org Subject: Re: [Users] presence module database tables
Hello,
the size of those columns was adjusted to match other tables -- it was
a
mistake in the documentation -- I have updated it: http://www.openser.org/docs/modules/1.2.x/presence.html#AEN199 http://openser.org/dokuwiki/doku.php/presence:database-tables
Thanks for reporting, Daniel
On 01/11/07 11:55, Cristian Caprar wrote:
Hi,
I am having trouble creating the xcap_xml table of the new presence module in mysql (latest 4.1.22 on RHEL 4).
The table definition from the docs is:
CREATE TABLE `xcap_xml` ( `user` varchar(256) NOT NULL, `domain` varchar(256) NOT NULL, `xcap` text NOT NULL, `doc_type` varchar(64) NOT NULL, PRIMARY KEY (`user`,`domain`,`doc_type`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1;
I get the following error: ERROR 1170 (42000): BLOB/TEXT column 'user' used in key
specification
without a key length
In my opinion, the problem is the definition of the user and domain columns, which are varchar(256), instead of varchar(255) and are automatically promoted to text columns. If changing the size to 255, everything is fine.
Does the presence db code do some length checks that can be affected
by
this change? Is the table definition correct or am I missing
something?
Thanks, Cristian
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
-
Cristian Caprar -
Daniel-Constantin Mierla