# Problem with inheritance mysql jabber server database

**URL:** <https://www.ruby-forum.com/t/problem-with-inheritance-mysql-jabber-server-database/133119>\
**Category:** Rails\
**Created:** [March 28, 2008, 1:27am UTC](https://www.ruby-forum.com/t/problem-with-inheritance-mysql-jabber-server-database/133119 "2008-03-28T01:27:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![casper\_the\_ghost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@casper\_the\_ghost](https://www.ruby-forum.com/u/casper_the_ghost)\
**Post date:** [March 28, 2008, 1:27am UTC](https://www.ruby-forum.com/t/problem-with-inheritance-mysql-jabber-server-database/133119/1 "2008-03-28T01:27:21Z")

</div>

rake db:migrate  
(in /var/www/jabber.myserver/jabber)  
rake aborted!  
Mysql::Error: You have an error in your SQL syntax; check the manual  
that corresponds to your MySQL server version for the right syntax to  
use near ‘-items’ at line 1: SHOW FIELDS FROM disco-items

(See full trace by running task with --trace)

this is the first time I encountra something like this… this DB is  
using mysql5 but it was build wehn mysql4  
and is been running fine with jabber for years, I just decided to do a  
RoR front end for users to create IM accounts.

Please help.

---

<div class="post-metadata">

**Author:** ![casper\_the\_ghost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@casper\_the\_ghost](https://www.ruby-forum.com/u/casper_the_ghost)\
**Post date:** [March 29, 2008, 7:05am UTC](https://www.ruby-forum.com/t/problem-with-inheritance-mysql-jabber-server-database/133119/2 "2008-03-29T07:05:57Z")

</div>

rek2  
escribió:\> rake db:migrate

> and is been running fine with jabber for years, I just decided to do a  
> RoR front end for users to create IM accounts.
> 
> Please help.

I still have not found anyplace were I get this SQL error under RoR…  
any idea were to look? I am not sure if this error is related to a non  
valid Rails DB scheme or a sql error…  
is confusing …
