Search bug on JForum 2.1.5 (solved)

[Migrated From Jforum.net]

Hello all!

We were getting a bug on some searches here. The problem was:

java.sql.SQLException: ERROR: value too long for type character varying(60)
	at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1471)
	at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1256)
	at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:175)
	at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:392)
	at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:330)
	at org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:282)
	at net.jforum.dao.generic.GenericSearchDAO.selectTopicData(GenericSearchDAO.java:234)
	at net.jforum.dao.generic.GenericSearchDAO.topicsByKeyword(GenericSearchDAO.java:224)
	at net.jforum.dao.generic.GenericSearchDAO.search(GenericSearchDAO.java:81)
	at net.jforum.view.forum.SearchAction.search(SearchAction.java:187)
	... 24 more

Going through the source code I found that the SQL statement defined in the file WEB-INF/config/database/generic/generic_queries.sql whose key is SearchModel.selectTopicData was inserting the result of a select from jforum_topics into the table jforum_search_topics.

The problem is that the field topic_title was defined as varchar(60) in jforum_search_topics while it was actually a varchar(100) in jforum_topics. Changing varchar(60) to varchar(100) in jforum_search_topics solves the problem.

Hope it helps. ;-)
[originally posted on jforum.net by jau]

[Migrated From Jforum.net]

Hmm 2 years after I got the same error with jforum 2.1.7!

I did the DB fix manually but I don't understand why that fix wasn't integrated into the upgrade scripts. It's a very common use case! I guess it was a PostgreSQL only issue..
[originally posted on jforum.net by turman]

[Migrated From Jforum.net]

turman wrote:I did the DB fix manually but I don't understand why that fix wasn't integrated into the upgrade scripts.

Apparently the jforum_search_topics table is not used anymore in 2.1.8, it could explain...
[originally posted on jforum.net by turman]