[ejabberd] What is the maximum JID length supported by ejabberd?
toby at telegraphics.com.au
Thu May 5 16:18:28 MSD 2011
On 05/05/11 12:52 AM, Eric Chamberlain wrote:
> MySQL has index key length limitations that are shorter than the max JID length. I was hoping there was some kind of a workaround in the mysql schema. And I wanted to make sure our user provisioning system supports what ejabberd supports in terms of valid JID lengths.
One possible workaround could be to store a hash, either as primary key,
or in a UNIQUE column while using an artificial primary key (such as an
> On May 4, 2011, at 9:41 PM, Shaun Kruger wrote:
>> I can't say that I have observed one in ejabberd's internals. I was
>> just reading string_to_jid() in jlib.erl and it doesn't appear to
>> enforce any sizes. I'm guessing it really is just an SQL schema
>> limitation. I expect that mnesia wouldn't be limited because it just
>> stores everything as native erlang terms.
>> What are you trying to accomplish? Which mysql tables are you using
>> that have the 250 character limit? I expect that you should be able
>> to change the table definition to increase the field size since I
>> can't see anything that enforces field sizes when using ejabberd_odbc.
>> On Wed, May 4, 2011 at 4:14 PM, Eric Chamberlain <eric at rf.com> wrote:
>>> My understanding from RFC3920 is that the JID node identifier can be up to 1023 bytes, but looking at the mysql schema, the jid must be less than 250 characters. Is that correct?
>>> What is the maximum JID length supported by ejabberd using mnesia, postgres, and mysql?
>>> Eric Chamberlain, Founder
>>> RF.com - http://RF.com/
>>> ejabberd mailing list
>>> ejabberd at jabber.ru
>> ejabberd mailing list
>> ejabberd at jabber.ru
> ejabberd mailing list
> ejabberd at jabber.ru
More information about the ejabberd