Note that there are some explanatory texts on larger screens.

plurals
  1. POField not inserting or updating , int type in sql
    primarykey
    data
    text
    <p>I am working on magento platform.I face a problem regarding values insertion to specific field: My query run perfect but one specific column not working for any query.I try my best but didn't find why .When i change the column type from int to varchar type it works.This is my table structure.</p> <pre><code>CREATE TABLE `followupemails_emaillogs` ( `id` int(8) NOT NULL AUTO_INCREMENT, `schedule_time` datetime DEFAULT NULL, `sent_time` datetime DEFAULT NULL, `email_status` varchar(100) DEFAULT NULL, `client_name` varchar(250) DEFAULT NULL, `client_email` varchar(250) DEFAULT NULL, `followupemails_id` int(11) DEFAULT NULL, PRIMARY KEY (`id`), UNIQUE KEY `id` (`id`) ) ENGINE=InnoDB AUTO_INCREMENT=30 DEFAULT CHARSET=latin1. </code></pre> <p>the "followupemails_id" column not working in insert and update query.This is one update query where record exist that id(29). <code>UPDATE followupemails_emaillogs SET followupemails_id=5 WHERE id =29</code>. This is insertion query <code>INSERT INTO followupemails_emaillogs SET followupemails_id=4, schedule_time='2013-10-23 08:10:00', email_status='pending', client_name='ayaz ali'</code>.this works fine on fiddle but not on my sqlyog ? what could be the issue.At last i find query that work perfect</p> <p><code>.INSERT INTO followupemails_emaillogs (followupemails_id,schedule_time,email_status,client_name,client_email) VALUES (26,'2013-10-23 08:10:00','pending','ayaz ali','mamhmood@yahoo.com');</code> Can anyone tell me why set query not working but second query works perfect.so that i can accept his answer.Thanks for all your help</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload