Весенний ботинок.Как правильно удалить дочернюю коллекцию @ManyToOne - PullRequest
Новая
       1

Весенний ботинок.Как правильно удалить дочернюю коллекцию @ManyToOne

0 голосов
/ 12 апреля 2019

У меня странный вопрос "должно быть", но как правильно справиться со случаем, когда у меня есть родитель и ребенок: 

@Entity
public class Parent {
   @Id
   private long id;

   @OneToMany(mappedBy = "parent")
   @Cascade(values = {CascadeType.PERSIST, CascadeType.REMOVE});// mysql db
   private List<Child> children = new LinkedList<Child>();// yea, this can be removed
}


@Entity
public class Child {
   @Id
   private long id;

   @ManyToOne
   @JoinColumn
   private Parent parent;
}

И вот что я обычно пытаюсь сделать:

public class SomeService {
    @Autowired
    private ParentDao parentDao;

    @Autowired
    private ChildDao childDao;

    @Transactional
    public void removeChildren(Parent parent) {
        // attempts #1
        childDao.removeAll(parent.getChildren());

        // attempts #2
        for(Child ch: parent.getChildren()) {childDao.removeById(ch.getId());}

        // attempts #3
        parent.getChildren().clear();
        parentDao.save(parent);
   }

При включенном ведении журнала hibernate sql я вижу, что ни одна из верхних попыток даже не пытается сделать оператор удаления - только "select ... from parentTable".И, конечно, все записи остаются.

DAO расширяются от JpaRepository<Parent\Child, Long>.

Для случая "Id" я даже пытался проверить существующую запись по id, и да -запись существовала.

Это имеет место в версиях Spring Boot как "1.4.1 RELEASE", так и "2.1.4 RELEASE".Может кто-нибудь сказать мне, что я делаю не так?(Удаление родителя работает, и каскад работает как следует для удаления).

Пример с выводом: 

@Override
    @Transactional
    public void cleanResourcesForParent(SessionConfig cfg) {
        logger.info("Removing resources for parent {}", cfg);

        for (Resource r : cfg.getResources()) {
            logger.info(">>> {}", r);
            logger.info("exist? {}", resourceDao.existsById(r.getId()));
            logger.info("Attempt 1");
            resourceDao.deleteById(r.getId());
            logger.info("Attempt 2");
            resourceDao.delete(r);
        }
        logger.info("Attempt 3");
        resourceDao.deleteAll(cfg.getResources());

        logger.info("flush");
        resourceDao.flush();
        /*
         * cfg.getResources().clear(); sessionConfigDao.saveAndFlush(cfg);
         */
    }

Parent - SessionConfig, child - Resource (отображается как session_config_resource наDB).

Вывод: 

Hibernate: select resources0_.parent_id as parent_i3_10_0_, resources0_.id as id1_10_0_, resources0_.id as id1_10_1_, resources0_.line as line2_10_1_, resources0_.parent_id as parent_i3_10_1_ from session_config_resource resources0_ where resources0_.parent_id=?
2019-04-12 14:35:35 INFO  [scheduling-1] SessionConfigServiceImpl.resolveSessionConfig: Updating C:\IpPhoneAutomation\ATA\ConfigSession\GLAnton\Sanity450LyncContactPictureConfig.tcl. Sync file date: 1545995407645, file last modif: 1545995407645
2019-04-12 14:35:35 INFO  [scheduling-1] ResourceService.cleanResourcesForParent: Removing resources for parent SessionConfig [id=1096, configName=Sanity450LyncContactPictureConfig.tcl, modified=1545995407645, resources=6]
2019-04-12 14:35:35 INFO  [scheduling-1] ResourceService.cleanResourcesForParent: >>> Resource [id=1097, parent=SessionConfig [id=1096, configName=Sanity450LyncContactPictureConfig.tcl, modified=1545995407645, resources=6], line=0]
Hibernate: select count(*) as col_0_0_ from session_config_resource resource0_ where resource0_.id=?
2019-04-12 14:35:35 INFO  [scheduling-1] ResourceService.cleanResourcesForParent: exist? true
2019-04-12 14:35:35 INFO  [scheduling-1] ResourceService.cleanResourcesForParent: Attempt 1
Hibernate: select resource0_.id as id1_10_0_, resource0_.line as line2_10_0_, resource0_.parent_id as parent_i3_10_0_, sessioncon1_.id as id1_9_1_, sessioncon1_.config_name as config_n2_9_1_, sessioncon1_.modified as modified3_9_1_ from session_config_resource resource0_ left outer join session_config sessioncon1_ on resource0_.parent_id=sessioncon1_.id where resource0_.id=?
Hibernate: select resources0_.parent_id as parent_i3_10_0_, resources0_.id as id1_10_0_, resources0_.id as id1_10_1_, resources0_.line as line2_10_1_, resources0_.parent_id as parent_i3_10_1_ from session_config_resource resources0_ where resources0_.parent_id=?
2019-04-12 14:35:35 INFO  [scheduling-1] ResourceService.cleanResourcesForParent: Attempt 2
Hibernate: select next_val as id_val from hibernate_sequence for update
Hibernate: update hibernate_sequence set next_val= ? where next_val=?
2019-04-12 14:35:35 INFO  [scheduling-1] ResourceService.cleanResourcesForParent: >>> Resource [id=1098, parent=SessionConfig [id=1096, configName=Sanity450LyncContactPictureConfig.tcl, modified=1545995407645, resources=6], line=1]
Hibernate: insert into session_config_resource (line, parent_id, id) values (?, ?, ?)
Hibernate: delete from session_config_resource where id=?
Hibernate: select count(*) as col_0_0_ from session_config_resource resource0_ where resource0_.id=?
2019-04-12 14:35:36 INFO  [scheduling-1] ResourceService.cleanResourcesForParent: exist? true
2019-04-12 14:35:36 INFO  [scheduling-1] ResourceService.cleanResourcesForParent: Attempt 1
2019-04-12 14:35:36 INFO  [scheduling-1] ResourceService.cleanResourcesForParent: Attempt 2
Hibernate: select next_val as id_val from hibernate_sequence for update
Hibernate: update hibernate_sequence set next_val= ? where next_val=?
2019-04-12 14:35:36 INFO  [scheduling-1] ResourceService.cleanResourcesForParent: >>> Resource [id=1099, parent=SessionConfig [id=1096, configName=Sanity450LyncContactPictureConfig.tcl, modified=1545995407645, resources=6], line=2]
Hibernate: insert into session_config_resource (line, parent_id, id) values (?, ?, ?)
Hibernate: delete from session_config_resource where id=?
Hibernate: select count(*) as col_0_0_ from session_config_resource resource0_ where resource0_.id=?
2019-04-12 14:35:36 INFO  [scheduling-1] ResourceService.cleanResourcesForParent: exist? true
2019-04-12 14:35:36 INFO  [scheduling-1] ResourceService.cleanResourcesForParent: Attempt 1
2019-04-12 14:35:36 INFO  [scheduling-1] ResourceService.cleanResourcesForParent: Attempt 2
Hibernate: select next_val as id_val from hibernate_sequence for update
Hibernate: update hibernate_sequence set next_val= ? where next_val=?
2019-04-12 14:35:36 INFO  [scheduling-1] ResourceService.cleanResourcesForParent: >>> Resource [id=1100, parent=SessionConfig [id=1096, configName=Sanity450LyncContactPictureConfig.tcl, modified=1545995407645, resources=6], line=3]
Hibernate: insert into session_config_resource (line, parent_id, id) values (?, ?, ?)
Hibernate: delete from session_config_resource where id=?
Hibernate: select count(*) as col_0_0_ from session_config_resource resource0_ where resource0_.id=?
2019-04-12 14:35:36 INFO  [scheduling-1] ResourceService.cleanResourcesForParent: exist? true
2019-04-12 14:35:36 INFO  [scheduling-1] ResourceService.cleanResourcesForParent: Attempt 1
2019-04-12 14:35:36 INFO  [scheduling-1] ResourceService.cleanResourcesForParent: Attempt 2
Hibernate: select next_val as id_val from hibernate_sequence for update
Hibernate: update hibernate_sequence set next_val= ? where next_val=?
2019-04-12 14:35:36 INFO  [scheduling-1] ResourceService.cleanResourcesForParent: >>> Resource [id=1101, parent=SessionConfig [id=1096, configName=Sanity450LyncContactPictureConfig.tcl, modified=1545995407645, resources=6], line=4]
Hibernate: insert into session_config_resource (line, parent_id, id) values (?, ?, ?)
Hibernate: delete from session_config_resource where id=?
Hibernate: select count(*) as col_0_0_ from session_config_resource resource0_ where resource0_.id=?
2019-04-12 14:35:36 INFO  [scheduling-1] ResourceService.cleanResourcesForParent: exist? true
2019-04-12 14:35:36 INFO  [scheduling-1] ResourceService.cleanResourcesForParent: Attempt 1
2019-04-12 14:35:36 INFO  [scheduling-1] ResourceService.cleanResourcesForParent: Attempt 2
Hibernate: select next_val as id_val from hibernate_sequence for update
Hibernate: update hibernate_sequence set next_val= ? where next_val=?
2019-04-12 14:35:36 INFO  [scheduling-1] ResourceService.cleanResourcesForParent: >>> Resource [id=1102, parent=SessionConfig [id=1096, configName=Sanity450LyncContactPictureConfig.tcl, modified=1545995407645, resources=6], line=5]
Hibernate: insert into session_config_resource (line, parent_id, id) values (?, ?, ?)
Hibernate: delete from session_config_resource where id=?
Hibernate: select count(*) as col_0_0_ from session_config_resource resource0_ where resource0_.id=?
2019-04-12 14:35:36 INFO  [scheduling-1] ResourceService.cleanResourcesForParent: exist? true
2019-04-12 14:35:36 INFO  [scheduling-1] ResourceService.cleanResourcesForParent: Attempt 1
2019-04-12 14:35:36 INFO  [scheduling-1] ResourceService.cleanResourcesForParent: Attempt 2
Hibernate: select next_val as id_val from hibernate_sequence for update
Hibernate: update hibernate_sequence set next_val= ? where next_val=?
2019-04-12 14:35:36 INFO  [scheduling-1] ResourceService.cleanResourcesForParent: Attempt 3
Hibernate: select next_val as id_val from hibernate_sequence for update
Hibernate: update hibernate_sequence set next_val= ? where next_val=?
2019-04-12 14:35:36 INFO  [scheduling-1] ResourceService.cleanResourcesForParent: flush
Hibernate: insert into session_config_resource (line, parent_id, id) values (?, ?, ?)
Hibernate: insert into session_config_resource (line, parent_id, id) values (?, ?, ?)
Hibernate: delete from session_config_resource where id=?
Hibernate: delete from session_config_resource where id=?
2019-04-12 14:35:36 INFO  [scheduling-1] SessionConfigServiceImpl.cacheSessionConfigData: Done

1 Ответ

0 голосов
/ 12 апреля 2019

И виновником (кажется, я неправильно понял назначение флага) была опция «удаление сироты», помеченная родителем: 

 @OneToMany(mappedBy = "parent", orphanRemoval = true)
   @Cascade(values = {CascadeType.PERSIST, CascadeType.REMOVE});
   private List<Child> children = new LinkedList<Child>();

Позволяет: 

parent.getChildren().clear(); 
parentDao.saveAndFlush(parent);

чтобы наконец положить конец этой проблеме.

Добро пожаловать на сайт PullRequest, где вы можете задавать вопросы и получать ответы от других членов сообщества.

Нет похожих вопросов

...