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

Alarms has not been created #54

Closed
ghost opened this issue May 13, 2013 · 8 comments
Closed

Alarms has not been created #54

ghost opened this issue May 13, 2013 · 8 comments

Comments

@ghost
Copy link

ghost commented May 13, 2013

One of the table names for alarms is 'maxvalue' which in the latest release of MySQL is a reserved SQL word. Getting SQL syntax error with this name in the SQL command.

@areski
Copy link
Member

areski commented May 13, 2013

Thanks for the report, this seems to be from mysql 5.5

@ghost
Copy link
Author

ghost commented May 13, 2013

Yes. You are right. From mysql 5.5.

Thanks

Leonard

From: Areski Belaid
Sent: Monday, May 13, 2013 9:10 AM
To: Star2Billing/a2billing
Cc: sanjap
Subject: Re: [a2billing] Alarms has not been created (#54)

Thanks for the report, this seems to be from mysql 5.5


Reply to this email directly or view it on GitHub.

@pablojmiranda
Copy link

Please any solutions??? Server are in production. This is the reason i'm not upgrade mysql server a2b.
Code modification?
Thanks

@areski
Copy link
Member

areski commented May 2, 2014

You are welcome to provide a patch/fix for this.

@pablojmiranda
Copy link

yes, if i fixed,I post the solution. I try and now the score is 3-0. I'm in 0 ;)

@Ubunter
Copy link

Ubunter commented Aug 29, 2016

Hello,
We have solved this bug...
It's because the alarms table, cc_alarm, has a column called maxvalue and it turns out that maxvalue is a keyword in mysql.

SOLUTION:
In ./admin/Public/form_data/FG_var_alarm.inc added backticks around maxvalue in the setup of $HD_Form -> FieldViewElement and $HD_Form -> FieldEditElement

Hope that we're right and correct, as it's working fine now, for us, and it's up to areski and the developers to prove this solution and close this bug.

Regards,

@areski
Copy link
Member

areski commented Aug 30, 2016

patch here: c879be4

@areski areski closed this as completed Aug 30, 2016
@mason-chase
Copy link

In my opinion: The all fields in entire statement should be enclosed with backticks. this will also improve MySQL parsing of any SQL statement.

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

4 participants