inconsistent use of case in table names in MySQL on Linux

with version 0.8RC3, we are finding errors with some of the queries
executed in the MySQL 5.051a database server

we find non-working options and when diving through the error log, there
are messages like the following one:

2009-03-27 13:40:00,202 [pool-4-thread-16] ERROR
o.o.a.d.record.dao.RecordingDaoImpl - getRecordingsByWhereClause: select c
from Recording as c where  ( c.rooms.rooms_id = 1  OR c.rooms.rooms_id = 2
 OR c.rooms.rooms_id = 3  OR c.rooms.rooms_id = 5  OR c.rooms.rooms_id = 4
 OR c.rooms.rooms_id = 6 ) AND  c.deleted != :deleted

what is happening is that the database creating SQL script creates tables
with names in lower case. But OpenMeetings (or Hibernate) sometimes tries
to get data using mixed case tablenames like "Recording", which with
databses in UNIX systems is not correct

MySQL allows us to enter a config value to lowercase every tablename, but
we cannot change the config as openmeetings is not the only app using that
database and the already existing databases would not find the existing
tables (usually in uppercase names) 

OpenMeetings should always use exactly the same tablename (same case) used
in the database creation script

Of course, with Windows and Mac installations, this is not a problem as
they are case insensity filesystem environments

Original issue reported on code.google.com by brive...@gmail.com on 27 Mar 2009 at 1:08

hoangduit / openmeetings

inconsistent use of case in table names in MySQL on Linux #666