We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi. Future story.(MySQL 5.5 ----> 5.6) I found it below.
-- MySQL5.6 NG INSERT INTO mail (id, email, html, template) VALUES ('', 'a', 'b', 1); -- Error Code: 1366. Incorrect integer value: '' for column 'id' at row 1
-- MySQL5.6 ok INSERT INTO mail ( id, email, html, template) VALUES ( null, 'a', 'b', 1); -- 1 row(s) affected
SET @@GLOBAL.sql_mode='';
or step by step. I change '' to null ( or 0).
/controller/admin/mailing.php 255 /controller/admin/newsletter.php 90 /controller/dashboard/projects.php 317 /library/feed.php 449 /library/mail.php 205 /library/mail.php 219 /library/sender.php 76 /library/sender.php 82 /model/user.php 287 if($data[':confirmed'] == ''){ $data[':confirmed'] = 0; } ...... :-)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi.
Future story.(MySQL 5.5 ----> 5.6) I found it below.
-- MySQL5.6 NG
INSERT INTO mail (id, email, html, template) VALUES ('', 'a', 'b', 1);
-- Error Code: 1366. Incorrect integer value: '' for column 'id' at row 1
-- MySQL5.6 ok
INSERT INTO mail ( id, email, html, template) VALUES ( null, 'a', 'b', 1);
-- 1 row(s) affected
I temporarily resolved. I remove strict mode.
SET @@GLOBAL.sql_mode='';
SELECT @@GLOBAL.sql_mode;
or step by step. I change '' to null ( or 0).
/controller/admin/mailing.php 255
/controller/admin/newsletter.php 90
/controller/dashboard/projects.php 317
/library/feed.php 449
/library/mail.php 205
/library/mail.php 219
/library/sender.php 76
/library/sender.php 82
/model/user.php 287
if($data[':confirmed'] == ''){
$data[':confirmed'] = 0;
}
...... :-)
The text was updated successfully, but these errors were encountered: