Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug when gammu-smsd start if [sql] table not named as default #78

Closed
m4ucoder opened this issue Dec 7, 2014 · 1 comment
Closed

Bug when gammu-smsd start if [sql] table not named as default #78

m4ucoder opened this issue Dec 7, 2014 · 1 comment
Assignees

Comments

@m4ucoder
Copy link

m4ucoder commented Dec 7, 2014

Hello,
This is a bug : if you rename tables used by gammu-smsd, you must also have "duplicated" tables with the 'original' name, because when gammu-smsd service starts, it look for tables with the original name.

Because I am developing a joomla component wich is using gammu-smsd, I have added [sql] into gammu-smsdrc file.
I had modified table names, because joomla uses table names with prefix. For instance the "outbox" table is renamed "ghuo3_outbox".

When I start gammu-smsd service, logs shows me :

Error code 1146, Error Table 'mydbjoomla.outbox' doesn't exist
SQL failure 2
Table outbox not found, disconnecting !

But if I add tables "outbox", "inbox" tables etc, and I restart gammu-smsd service, the problem dissapears.
The problem is that when the service begins, gammu-smsd make SELECT on "outbox", "inbox" etc, and after when initialization is done, it takes all prefixed table : "ghuo3_outbox", "ghuo3_inbox" etc. and works as expected.

I hoê this help somebody

Philippe Lambotte

@nijel
Copy link
Member

nijel commented Dec 29, 2014

Indeed changing table names in custom SQL queries is not supported right now...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants