📣 Magento_Newsletter · engine innodb

newsletter_subscriber

Newsletter Subscriber

Neighbourhood (1-hop foreign-key graph — showing 3 of 3)

flowchart LR
  c["newsletter_subscriber"]:::center
  n0["store"]
  click n0 "/schema/table/store"
  n0 -- store_id --> c
  n1["newsletter_problem"]
  click n1 "/schema/table/newsletter_problem"
  c -- subscriber_id --> n1
  n2["newsletter_queue_link"]
  click n2 "/schema/table/newsletter_queue_link"
  c -- subscriber_id --> n2
  click c "/schema/table/newsletter_subscriber"
  classDef center fill:#eef2ff,stroke:#6366f1,color:#3730a3,stroke-width:1.5px

Click a node to jump to that table.

Related tables (3)

store_id → store newsletter_problem → subscriber_id newsletter_queue_link → subscriber_id

Columns (7)

Name	Type	Null	Default	Comment
subscriber_id PK	int unsigned	no		Subscriber ID
store_id	smallint unsigned	yes	0	Store ID
change_status_at	timestamp	yes		Change Status At
customer_id	int unsigned	no	0	Customer ID
subscriber_email	varchar(150)	yes		Subscriber Email
subscriber_status	int	no	0	Subscriber Status
subscriber_confirm_code	varchar(32)	yes	NULL	Subscriber Confirm Code

Keys & indexes

Primary key: subscriber_id

Indexes

NEWSLETTER_SUBSCRIBER_CUSTOMER_ID (customer_id) btree
NEWSLETTER_SUBSCRIBER_STORE_ID (store_id) btree
NEWSLETTER_SUBSCRIBER_SUBSCRIBER_EMAIL (subscriber_email) btree

References (1)

store_id → store .store_id (on delete SET NULL)

Referenced by (2)

newsletter_problem .subscriber_id → .subscriber_id (on delete CASCADE)
newsletter_queue_link .subscriber_id → .subscriber_id (on delete CASCADE)