Answers.Body: <p>It is a foreign key to the civicrm_mailing_event_queue table. It is in lockstep since all your emails are being delivered etc and thence the two tables are in sync. However there is no guarantee of this and you cannot rely on it, hence the need of the foreign key.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-07T23:06:20.967Z
Answers.LastActivityDate: 2015-06-07T23:06:20.967Z
Answers.UserDisplayName: Donald Lobo
Body: <p>I generally find that the <em>event_queue_id</em> and <em>id</em> values are same for all the tuples in the <strong>civicrm_mailing_event_delivered</strong> table. Why do we need a separate event_queue_id then? Can two tuples in this table have the same event_queue_id?</p>
  
Tags: <civimail><cron-job><mysql><gsoc>
Title: What is the significance of event_queue_id in civicrm_mailing_event_delivered table?
ThreadText: # What is the significance of event_queue_id in civicrm_mailing_event_delivered table?
  
  (Asked by: username_0 on 2015-06-07)
  
  I generally find that the *event\_queue\_id* and *id* values are same for all the tuples in the **civicrm\_mailing\_event\_delivered** table. Why do we need a separate event\_queue\_id then? Can two tuples in this table have the same event\_queue\_id?
  
  **Tags:** civimail, cron-job, mysql, gsoc
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-06-07. Score: 1
  
  It is a foreign key to the civicrm\_mailing\_event\_queue table. It is in lockstep since all your emails are being delivered etc and thence the two tables are in sync. However there is no guarantee of this and you cannot rely on it, hence the need of the foreign key.
  
  
  ---
  
  