[
https://issues.jboss.org/browse/JGRP-1345?page=com.atlassian.jira.plugin....
]
Sanne Grinovero commented on JGRP-1345:
---------------------------------------
Hi Raúl,
what is the important difference between the two statements? It looks like you only
selected the ENGINE and charset options, but that are non-standard options of MySQL; also
you're using "IF NOT EXISTS", which is alas non standard as well, and while
it is a nice to have, it's not needed as JGroups won't fail if the table creation
fails - assuming it failed because the table already existed.
The default SQL statement is using standard SQL only on purpose: I can't change that
or it will break all other databases.
I had tested it on MySQL but I was using InnoDB as default engine, also I have the habit
to always use those utf8 charsets and collations (specified in the global configuration
file of the database server and client).
I think it's very likely that people will have to customize the SQL statements for
each case, so I'm not considering this as a bug as the default configuration
doesn't work on MySQL, but it works fine when configured properly.
What do you suggest I could do to clarify this or make it easier? I'll add your SQL
initialization to the WIKI page of JDBC_PING.
JDBC_PING fails to initialize table in mysql
--------------------------------------------
Key: JGRP-1345
URL:
https://issues.jboss.org/browse/JGRP-1345
Project: JGroups
Issue Type: Bug
Affects Versions: 2.12
Reporter: Raúl Raja Martínez
Assignee: Sanne Grinovero
Fix For: 2.12.2, 3.0
JDBC_PING fails to initialize DB table for discover when executing the following SQL:
CREATE TABLE JGROUPSPING (own_addr varchar(200) NOT NULL, cluster_name varchar(200) NOT
NULL, ping_data varbinary(5000) DEFAULT NULL, PRIMARY KEY (own_addr, cluster_name) )
The statement results in "Specified key was too long; max key length is 1000
bytes"
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira