Data can't be deleted because it's still used by another data

[mootensai]

Data can't be deleted because it's still used by another data

[mootensai]

could you give me the SQL related to that table?

[RGTimothy]

CREATE TABLE IF NOT EXISTS `sales_key_focus_plan` (
  `id` int(11) NOT NULL AUTO_INCREMENT COMMENT 'ID',
  `user_id` int(11) NOT NULL COMMENT 'Sales Name',
  `date_from` date NOT NULL COMMENT 'From',
  `date_to` date NOT NULL COMMENT 'To',
  PRIMARY KEY (`id`),
  KEY `user_id` (`user_id`),
  CONSTRAINT `FK_sales_key_focus_plan_user` FOREIGN KEY (`user_id`) REFERENCES `user` (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=8 DEFAULT CHARSET=latin1;

CREATE TABLE IF NOT EXISTS `sales_key_focus_plan_detail` (
  `id` int(11) NOT NULL AUTO_INCREMENT COMMENT 'ID',
  `sales_key_focus_plan_id` int(11) NOT NULL DEFAULT '0' COMMENT 'Focus Plan ID',
  `customer` varchar(100) NOT NULL COMMENT 'Customer',
  `objective` text NOT NULL COMMENT 'Objectives',
  `appointment_datetime` datetime DEFAULT NULL COMMENT 'Appointment Date/Time',
  `remarks` text COMMENT 'Remarks',
  PRIMARY KEY (`id`),
  KEY `sales_key_focus_plan_id` (`sales_key_focus_plan_id`),
  CONSTRAINT `FK_sales_key_focus_plan_detail_sales_key_focus_plan` FOREIGN KEY (`sales_key_focus_plan_id`) REFERENCES `sales_key_focus_plan` (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

[mootensai]

does the table sales_key_focus_plan_detail is related to another table?

On Wed, Feb 24, 2016 at 9:18 AM, Ronal Gorba Timothy <
[email protected]> wrote:

---

-- Host: 127.0.0.1
-- Server version: 5.6.17 - MySQL Community Server (GPL)
-- Server OS: Win64
-- HeidiSQL Version: 9.1.0.4867

---

/!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/!40101 SET NAMES utf8mb4 /;
/!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 /;
/!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;

-- Dumping structure for table sysnet_v2.sales_key_focus_plan
CREATE TABLE IF NOT EXISTS sales_key_focus_plan (
id int(11) NOT NULL AUTO_INCREMENT COMMENT 'ID',
user_id int(11) NOT NULL COMMENT 'Sales Name',
date_from date NOT NULL COMMENT 'From',
date_to date NOT NULL COMMENT 'To',
PRIMARY KEY (id),
KEY user_id (user_id),
CONSTRAINT FK_sales_key_focus_plan_user FOREIGN KEY (user_id) REFERENCES user (id)
) ENGINE=InnoDB AUTO_INCREMENT=8 DEFAULT CHARSET=latin1;

-- Dumping data for table sysnet_v2.sales_key_focus_plan: ~0 rows (approximately)
/!40000 ALTER TABLE sales_key_focus_plan DISABLE KEYS */;
/!40000 ALTER TABLE sales_key_focus_plan ENABLE KEYS */;

-- Dumping structure for table sysnet_v2.sales_key_focus_plan_detail
CREATE TABLE IF NOT EXISTS sales_key_focus_plan_detail (
id int(11) NOT NULL AUTO_INCREMENT COMMENT 'ID',
sales_key_focus_plan_id int(11) NOT NULL DEFAULT '0' COMMENT 'Focus Plan ID',
customer varchar(100) NOT NULL COMMENT 'Customer',
objective text NOT NULL COMMENT 'Objectives',
appointment_datetime datetime DEFAULT NULL COMMENT 'Appointment Date/Time',
remarks text COMMENT 'Remarks',
PRIMARY KEY (id),
KEY sales_key_focus_plan_id (sales_key_focus_plan_id),
CONSTRAINT FK_sales_key_focus_plan_detail_sales_key_focus_plan FOREIGN KEY (sales_key_focus_plan_id) REFERENCES sales_key_focus_plan (id)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

-- Dumping data for table sysnet_v2.sales_key_focus_plan_detail: ~0 rows (approximately)
/!40000 ALTER TABLE sales_key_focus_plan_detail DISABLE KEYS */;
/!40000 ALTER TABLE sales_key_focus_plan_detail ENABLE KEYS /;
/!40101 SET SQL_MODE=IFNULL(@OLD_SQL_MODE, '') /;
/!40014 SET FOREIGN_KEY_CHECKS=IF(@OLD_FOREIGN_KEY_CHECKS IS NULL, 1, @OLD_FOREIGN_KEY_CHECKS) /;
/!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;

—
Reply to this email directly or view it on GitHub
#43 (comment)
.

[RGTimothy]

No, its not. That table just has 1 foreign key (sales_key_focus_plan_id) with its reference table : "sales_key_focus_plan.id"

[mootensai]

OK, the problem is on mootensai/yii2-relation-trait

I've fix that bug, please try to update & use the dev version

i don't know if this works
composer update mootensai/yii2-relation-trait:@dev
if it don't work, then

composer remove mootensai/yii2-relation-trait

composer require mootensai/yii2-relation-trait:@dev

[RGTimothy]

Do I have to regenerate the CRUD with enhanced-gii?

[mootensai]

No, you don't have to

On Wed, Feb 24, 2016 at 9:45 AM, Ronal Gorba Timothy <
[email protected]> wrote:

Do I have to regenerate the CRUD with enhanced-gii?

—
Reply to this email directly or view it on GitHub
#43 (comment)
.

[RGTimothy]

Splendid! Its working now. Thanks.