主頁 > 作業系統 > 更新@OneToMany關系(SpringBoot、SpringData)

更新@OneToMany關系(SpringBoot、SpringData)

2021-11-02 09:00:01 作業系統

我有一個OneToMany關系(兩個表雙向)。當我保存醫生的專業時,它確實有效,但是當我洗掉任何專業并更新醫生時,它不起作用。

醫生

@Entity
@Table(name = "doctors")
public class Doctor implements Serializable {

    private static final long serialVersionUID = 1L;

    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    private Integer doctorId;

    @Column(length = 20)
    private String doctorName;

    @Column(length = 9)
    private String doctorPhoneNo;

    @Column(length = 30)
    private String doctorEmailAddress;

    private String doctorProfileImage;

    @Enumerated(EnumType.STRING)
    private Status status;

    @Column(length = 6)
    private String doctorCmp;

    @OneToMany(mappedBy = "doctor", cascade = CascadeType.ALL)
//  @JsonIgnore
    private Set<DoctorSpecialties> doctorSpecialties;

    public Doctor() {
        this.doctorSpecialties = new HashSet<>();
    }

    public Doctor(Integer id){
        this();
        this.doctorId = id;
    }

    // getters y setters
}

專業

@Entity
@Table(name = "specialties")
public class Specialty implements Serializable {

    private static final long serialVersionUID = 1L;

    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    private Integer specialtyId;

    private String specialtyName;

    @OneToMany(mappedBy = "specialty")
    @JsonIgnore
    private Set<DoctorSpecialties> doctorSpecialties;

    public Specialty() {
    }

    public Specialty(Integer id) {
        this.specialtyId = id;
    }

    // getters and setters
  }

醫生專長

@Entity
@Table(name = "doctor_specialties")
public class DoctorSpecialties implements Serializable {

    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    private Integer id;

    @ManyToOne(fetch = FetchType.LAZY)
    @JoinColumn(name = "doctor_id")
    private Doctor doctor;

    @ManyToOne(fetch = FetchType.LAZY)
    @JoinColumn(name = "specialty_id")
    private Specialty specialty;

    @OneToMany
    @JoinColumn(name = "doctor_specialties_id")
    private Set<Appointment> appointments;

    @OneToMany
    @JoinColumn(name = "doctor_specialties_id")
    private Set<DoctorSchedule> schedules;

    public DoctorSpecialties(){

    }

    public DoctorSpecialties(Specialty specialty, Doctor doctor){
        this.specialty = specialty;
        this.doctor = doctor;
    }
      getters / setters
 }

控制器

@PostMapping(value = "/saveSpecialties/{id}")
public String saveDoctorSpecialties(@RequestParam(required = false) String[] specialtiesId,
                                    @PathVariable Integer id, RedirectAttributes message) {

    if (id != null && id > 0) {
        Doctor doctor = doctorService.findOne(id);

        if (doctor != null) {

            // It does not work
            doctor.getDoctorSpecialties().forEach(ds -> doctorSpecialtiesService.delete(ds.getId()));

            doctor.getDoctorSpecialties().clear();

            if (specialtiesId != null) {
                for (String specialtyId : specialtiesId) {
                    DoctorSpecialties ds = new DoctorSpecialties();
                    ds.setSpecialty(new Specialty(Integer.parseInt(specialtyId)));
                       
                    ds.setDoctor(doctor);

                    doctor.getDoctorSpecialties()
                            .add(ds);
                }
                
            }
            doctorService.update(doctor);
            message.addFlashAttribute("success", "Specialties successfully saved.");
            return "redirect:/doctors/profile/{id}/specialties";
        }
    }
    // specialtiesId = new String[]{};
    message.addFlashAttribute("error", "Doctor doesn't exists");
    return "redirect:/doctors/list";
}

安慰:

2021-10-30 21:19:13.330 DEBUG 44504 --- [nio-8080-exec-7] org.hibernate.SQL : select doctor0_.doctor_id as doctor_i1_3_0_, doctor0_.doctor_cmp as doctor_c2_3_0_, doctor0_.doctor_email_address as doctor_e3_3_0_, doctor0_.doctor_name as doctor_n4_3_0_, doctor0_.doctor_phone_no as doctor_p5_3_0_, doctor0_.doctor_profile_image as doctor_p6_3_0_, doctor0_.status as status7_3_0_ from doctors doctor0_ where doctor0_.doctor_id=? 2021-10-30 21:19:13.339 DEBUG 44504 --- [nio-8080-exec-7] org.hibernate.SQL : select doctorspec0_.doctor_id as doctor_i2_2_0_, doctorspec0_.id as id1_2_0_, doctorspec0_.id as id1_2_1_, doctorspec0_.doctor_id as doctor_i2_2_1_, doctorspec0_.specialty_id as specialt3_2_1_ from doctor_specialties doctorspec0_ where doctorspec0_.doctor_id=? 2021-10-30 21:19:13.401 DEBUG 44504 --- [nio-8080-exec-8] org.hibernate.SQL : select doctor0_.doctor_id as doctor_i1_3_0_, doctor0_.doctor_cmp as doctor_c2_3_0_, doctor0_.doctor_email_address as doctor_e3_3_0_, doctor0_.doctor_name as doctor_n4_3_0_, doctor0_.doctor_phone_no as doctor_p5_3_0_, doctor0_.doctor_profile_image as doctor_p6_3_0_, doctor0_.status as status7_3_0_ from doctors doctor0_ where doctor0_.doctor_id=? 2021-10-30 21:19:13.404 DEBUG 44504 --- [nio-8080-exec-8] org.hibernate.SQL : select specialty0_.specialty_id as specialt1_7_0_, doctorspec1_.id as id1_2_1_, doctor2_.doctor_id as doctor_i1_3_2_, specialty0_.specialty_name as specialt2_7_0_, doctorspec1_.doctor_id as doctor_i2_2_1_, doctorspec1_.specialty_id as specialt3_2_1_, doctorspec1_.specialty_id as specialt3_2_0__, doctorspec1_.id as id1_2_0__, doctor2_.doctor_cmp as doctor_c2_3_2_, doctor2_.doctor_email_address as doctor_e3_3_2_, doctor2_.doctor_name as doctor_n4_3_2_, doctor2_.doctor_phone_no as doctor_p5_3_2_, doctor2_.doctor_profile_image as doctor_p6_3_2_, doctor2_.status as status7_3_2_ from specialties specialty0_ inner join doctor_specialties doctorspec1_ on specialty0_.specialty_id=doctorspec1_.specialty_id inner join doctors doctor2_ on doctorspec1_.doctor_id=doctor2_.doctor_id where doctor2_.doctor_id=? 2021-10-30 21:19:13.565 DEBUG 44504 --- [nio-8080-exec-4] org.hibernate.SQL : select specialty0_.specialty_id as specialt1_7_0_, doctorspec1_.id as id1_2_1_, doctor2_.doctor_id as doctor_i1_3_2_, specialty0_.specialty_name as specialt2_7_0_, doctorspec1_.doctor_id as doctor_i2_2_1_, doctorspec1_.specialty_id as specialt3_2_1_, doctorspec1_.specialty_id as specialt3_2_0__, doctorspec1_.id as id1_2_0__, doctor2_.doctor_cmp as doctor_c2_3_2_, doctor2_.doctor_email_address as doctor_e3_3_2_, doctor2_.doctor_name as doctor_n4_3_2_, doctor2_.doctor_phone_no as doctor_p5_3_2_, doctor2_.doctor_profile_image as doctor_p6_3_2_, doctor2_.status as status7_3_2_ from specialties specialty0_ inner join doctor_specialties doctorspec1_ on specialty0_.specialty_id=doctorspec1_.specialty_id inner join doctors doctor2_ on doctorspec1_.doctor_id=doctor2_.doctor_id where doctor2_.doctor_id=?

There is no delete statement...

------------------------ EDIT 1 ------------------------

Doctor find = doctorRepository.findById(1).get();
    
DoctorSpecialties ds1 = new DoctorSpecialties();
ds1.setSpecialty(specialtyRepository.findById(1).get());
ds1.setDoctor(find);
    
DoctorSpecialties ds2 = new DoctorSpecialties();
ds2.setSpecialty(specialtyRepository.findById(2).get());
ds2.setDoctor(find);
    
find.getDoctorSpecialties().add(ds1);
find.getDoctorSpecialties().add(ds2);

doctorRepository.save(find);

I have done some tests and I can not understand completely. I did and it only saves once when actually I am adding two objects.

insert into doctor_specialties (id, doctor_id, specialty_id) values (null, ?, ?)

------------------------ EDIT 2 ------------------------

DoctorSpecialties (Modify the constructor)

@Entity
@Table(name = "doctor_specialties")
public class DoctorSpecialties implements Serializable {

    public DoctorSpecialties(Integer specialtyId, Doctor doctor) {
        this.specialty = new Specialty(specialtyId);
        this.doctor = doctor;
    }

 }

Controller

@PostMapping(value = "/saveSpecialties/{id}")
public String saveDoctorSpecialties(@RequestParam(required = false) String[] specialtiesId,
                                    @PathVariable Integer id, RedirectAttributes message) {
    if (id != null && id > 0) {

        doctorService.saveDelete(id);

        Doctor doctor = doctorService.findOne(id);
        if (specialtiesId != null && specialtiesId.length > 0) {
            for(String idSpecialty : specialtiesId){
                doctorSpecialtiesService.save(new DoctorSpecialties(Integer.parseInt(idSpecialty), doctor));
            }
        }
        message.addFlashAttribute("success", "Specialties successfully saved.");
        return "redirect:/doctors/profile/{id}/specialties";
    }
    message.addFlashAttribute("error", "Doctor doesn't exists");
    return "redirect:/doctors/list";
}

Service

@Override
@Transactional
public void saveDelete(Integer doctorId) {
    Doctor doctor = this.doctorRepository
            .findById(doctorId).get();
    doctor.getDoctorSpecialties().clear();
}

Console:

選擇doctor0_.doctor_id如doctor_i1_3_0_,從醫生doctor0_ doctor0_.doctor_cmp如doctor_c2_3_0_,doctor0_.doctor_email_address如doctor_e3_3_0_,doctor0_.doctor_name如doctor_n4_3_0_,doctor0_.doctor_phone_no如doctor_p5_3_0_,doctor0_.doctor_profile_image如doctor_p6_3_0_,doctor0_.status如status7_3_0_其中doctor0_.doctor_id = ? 選擇doctorspec0_.doctor_id作為doctor_i2_2_0_,doctorspec0_.id作為id1_2_0_,doctorspec0_.id作為id1_2_1_,doctorspec0_.doctor_id作為doctor_i2_2_1_,doctorspec0_.specialty_id作為specialt3_2_1_來自doctor_specialties_doctorspec_doctor_spec0

更新預約 set doctor_specialties_id=null where doctor_specialties_id=?

更新doctor_schedules 設定doctor_specialties_id=null 哪里doctor_specialties_id=?

從doctor_specialties 中洗掉id=?

uj5u.com熱心網友回復:

有的一方mappedBy就是擁有的一方。

這意味著類似于:“關系這一側的修改已經映射到關系的另一側,因此無需在額外的表中單獨跟蹤它。”

檢查此 url 以獲取更多資訊ORM 映射中的“擁有方”是什么?

uj5u.com熱心網友回復:

對于事務中的一對多關系,一旦你得到了父(Doctor)并回圈了它的子(DoctorSpecialties)[換句話說,一旦你將整個父和它的子加載到 Persistent 狀態],你將無法DoctorSpecialties直接通過它洗掉你repository


您可以嘗試類似下面的示例來查看它:

@Transactional
public void removeLine(Long doctorId, Long specId) {
    Doctor doctor = this.doctorRepository  // (1)
        .findById(doctorId)
        .orElseThrow(IllegalArgumentException::new);
    this.doctorSpecialtiesRepository.deleteById(specId); // (2)
}

在 (1) 處,我們加載doctor到持久狀態。所以在這里,如果fetch = FetchType.EAGER,這意味著它將加載doctor并全部doctorSpecialties進入持久狀態,并且這個原因(2)不會給你任何影響。

否則,如果fetch = FetchType.LAZY,則僅加載doctor到持久狀態,并且在(2)處將成功洗掉。

您的情況類似,fetch = FetchType.LAZY但您通過 using 回圈了孩子,forEach并加載doctorSpecialties到持久狀態。這就是您無法洗掉它們的原因。


建議:orphanRemoval = true在您的父物體中使用

@OneToMany(mappedBy = "doctor", cascade = CascadeType.ALL, orphanRemoval = true)
    private Set<DoctorSpecialties> dss;

只需在您的方法中清除其子項(在@Transactional 方法中)

doctor.getDoctorSpecialties().clear();

轉載請註明出處,本文鏈接:https://www.uj5u.com/caozuo/344082.html

標籤:爪哇 弹簧靴 弹簧数据-jpa

上一篇:使用gradle時,在Spring啟動測驗期間無法加載驅動程式類:“org.h2.Driver”

下一篇:SpringWebClient檢索包裹在results屬性下的json物件

標籤雲
其他(157675) Python(38076) JavaScript(25376) Java(17977) C(15215) 區塊鏈(8255) C#(7972) AI(7469) 爪哇(7425) MySQL(7132) html(6777) 基礎類(6313) sql(6102) 熊猫(6058) PHP(5869) 数组(5741) R(5409) Linux(5327) 反应(5209) 腳本語言(PerlPython)(5129) 非技術區(4971) Android(4554) 数据框(4311) css(4259) 节点.js(4032) C語言(3288) json(3245) 列表(3129) 扑(3119) C++語言(3117) 安卓(2998) 打字稿(2995) VBA(2789) Java相關(2746) 疑難問題(2699) 细绳(2522) 單片機工控(2479) iOS(2429) ASP.NET(2402) MongoDB(2323) 麻木的(2285) 正则表达式(2254) 字典(2211) 循环(2198) 迅速(2185) 擅长(2169) 镖(2155) 功能(1967) .NET技术(1958) Web開發(1951) python-3.x(1918) HtmlCss(1915) 弹簧靴(1913) C++(1909) xml(1889) PostgreSQL(1872) .NETCore(1853) 谷歌表格(1846) Unity3D(1843) for循环(1842)

熱門瀏覽
  • CA和證書

    1、在 CentOS7 中使用 gpg 創建 RSA 非對稱密鑰對 gpg --gen-key #Centos上生成公鑰/密鑰對(存放在家目錄.gnupg/) 2、將 CentOS7 匯出的公鑰,拷貝到 CentOS8 中,在 CentOS8 中使用 CentOS7 的公鑰加密一個檔案 gpg -a ......

    uj5u.com 2020-09-10 00:09:53 more
  • Kubernetes K8S之資源控制器Job和CronJob詳解

    Kubernetes的資源控制器Job和CronJob詳解與示例 ......

    uj5u.com 2020-09-10 00:10:45 more
  • VMware下安裝CentOS

    VMware下安裝CentOS 一、軟硬體準備 1 Centos鏡像準備 1.1 CentOS鏡像下載地址 下載地址 1.2 CentOS鏡像下載程序 點擊下載地址進入如下圖的網站,選擇需要下載的版本,這里選擇的是Centos8,點擊如圖所示。 決定選擇Centos8后,選擇想要的鏡像源進行下載,此 ......

    uj5u.com 2020-09-10 00:12:10 more
  • 如何使用Grep命令查找多個字串

    如何使用Grep 命令查找多個字串 大家好,我是良許! 今天向大家介紹一個非常有用的技巧,那就是使用 grep 命令查找多個字串。 簡單介紹一下,grep 命令可以理解為是一個功能強大的命令列工具,可以用它在一個或多個輸入檔案中搜索與正則運算式相匹配的文本,然后再將每個匹配的文本用標準輸出的格式 ......

    uj5u.com 2020-09-10 00:12:28 more
  • git配置http代理

    git配置http代理 經常遇到克隆 github 慢的問題,這里記錄一下幾種配置 git 代理的方法,解決 clone github 過慢。 目錄 git配置代理 git單獨配置github代理 git配置全域代理 配置終端環境變數 git配置代理 主要使用 git config 命令 git單獨 ......

    uj5u.com 2020-09-10 00:12:33 more
  • Linux npm install 裝包時提示Error EACCES permission denied解

    npm install 裝包時提示Error EACCES permission denied解決辦法 ......

    uj5u.com 2020-09-10 00:12:53 more
  • Centos 7下安裝nginx,使用yum install nginx,提示沒有可用的軟體包

    Centos 7下安裝nginx,使用yum install nginx,提示沒有可用的軟體包。 18 (flaskApi) [root@67 flaskDemo]# yum -y install nginx 19 已加載插件:fastestmirror, langpacks 20 Loading ......

    uj5u.com 2020-09-10 00:13:13 more
  • Linux查看服務器暴力破解ssh IP

    在公網的服務器上經常遇到別人爆破你服務器的22埠,用來挖礦或者干其他嘿嘿嘿的事情~ 這種情況下正確的做法是: 修改默認ssh的22埠 使用設定密鑰登錄或者白名單ip登錄 建議服務器密碼為復雜密碼 創建普通用戶登錄服務器(root權限過大) 建立堡壘機,實作統一管理服務器 統計爆破IP [root ......

    uj5u.com 2020-09-10 00:13:17 more
  • CentOS 7系統常見快捷鍵操作方式

    Linux系統中一些常見的快捷方式,可有效提高操作效率,在某些時刻也能避免操作失誤帶來的問題。 ......

    uj5u.com 2020-09-10 00:13:31 more
  • CentOS 7作業系統目錄結構介紹

    作業系統存在著大量的資料檔案資訊,相應檔案資訊會存在于系統相應目錄中,為了更好的管理資料資訊,會將系統進行一些目錄規劃,不同目錄存放不同的資源。 ......

    uj5u.com 2020-09-10 00:13:35 more
最新发布
  • vim的常用命令

    Vim的6種基本模式 1. 普通模式在普通模式中,用的編輯器命令,比如移動游標,洗掉文本等等。這也是Vim啟動后的默認模式。這正好和許多新用戶期待的操作方式相反(大多數編輯器默認模式為插入模式)。 2. 插入模式在這個模式中,大多數按鍵都會向文本緩沖中插入文本。大多數新用戶希望文本編輯器編輯程序中一 ......

    uj5u.com 2023-04-20 08:43:21 more
  • vim的常用命令

    Vim的6種基本模式 1. 普通模式在普通模式中,用的編輯器命令,比如移動游標,洗掉文本等等。這也是Vim啟動后的默認模式。這正好和許多新用戶期待的操作方式相反(大多數編輯器默認模式為插入模式)。 2. 插入模式在這個模式中,大多數按鍵都會向文本緩沖中插入文本。大多數新用戶希望文本編輯器編輯程序中一 ......

    uj5u.com 2023-04-20 08:42:36 more
  • docker學習

    ###Docker概述 真實專案部署環境可能非常復雜,傳統發布專案一個只需要一個jar包,運行環境需要單獨部署。而通過Docker可將jar包和相關環境(如jdk,redis,Hadoop...)等打包到docker鏡像里,將鏡像發布到Docker倉庫,部署時下載發布的鏡像,直接運行發布的鏡像即可。 ......

    uj5u.com 2023-04-19 09:26:53 more
  • 設定Windows主機的瀏覽器為wls2的默認瀏覽器

    這里以Chrome為例。 1. 準備作業 wsl是可以使用Windows主機上安裝的exe程式,出于安全考慮,默認情況下改功能是無法使用。要使用的話,終端需要以管理員權限啟動。 我這里以Windows Terminal為例,介紹如何默認使用管理員權限打開終端,具體操作如下圖所示: 2. 操作 wsl ......

    uj5u.com 2023-04-19 09:25:49 more
  • docker學習

    ###Docker概述 真實專案部署環境可能非常復雜,傳統發布專案一個只需要一個jar包,運行環境需要單獨部署。而通過Docker可將jar包和相關環境(如jdk,redis,Hadoop...)等打包到docker鏡像里,將鏡像發布到Docker倉庫,部署時下載發布的鏡像,直接運行發布的鏡像即可。 ......

    uj5u.com 2023-04-19 09:19:04 more
  • Linux學習筆記

    IP地址和主機名 IP地址 ifconfig可以用來查詢本機的IP地址,如果不能使用,可以通過install net-tools安裝。 Centos系統下ens33表示主網卡;inet后表示IP地址;lo表示本地回環網卡; 127.0.0.1表示代指本機;0.0.0.0可以用于代指本機,同時在放行設 ......

    uj5u.com 2023-04-18 06:52:01 more
  • 解決linux系統的kdump服務無法啟動的問題

    問題:專案麒麟系統服務器的kdump服務無法啟動,沒有相關日志無法定位問題。 1、查看服務狀態是關閉的,重啟系統也無法啟動 systemctl status kdump 2、修改grub引數,修改“crashkernel”為“512M(有的機器數值太大太小都會導致報錯,建議從128M開始試,或者加個 ......

    uj5u.com 2023-04-12 09:59:50 more
  • 解決linux系統的kdump服務無法啟動的問題

    問題:專案麒麟系統服務器的kdump服務無法啟動,沒有相關日志無法定位問題。 1、查看服務狀態是關閉的,重啟系統也無法啟動 systemctl status kdump 2、修改grub引數,修改“crashkernel”為“512M(有的機器數值太大太小都會導致報錯,建議從128M開始試,或者加個 ......

    uj5u.com 2023-04-12 09:59:01 more
  • 你是不是暴露了?

    作者:袁首京 原創文章,轉載時請保留此宣告,并給出原文連接。 如果您是計算機相關從業人員,那么應該經歷不止一次網路安全專項檢查了,你肯定是收到過資訊系統技術檢測報告,要求你加強風險監測,確保你提供的系統服務堅實可靠了。 沒檢測到問題還好,檢測到問題的話,有些處理起來還是挺麻煩的,尤其是線上正在運行的 ......

    uj5u.com 2023-04-05 16:52:56 more
  • 細節拉滿,80 張圖帶你一步一步推演 slab 記憶體池的設計與實作

    1. 前文回顧 在之前的幾篇記憶體管理系列文章中,筆者帶大家從宏觀角度完整地梳理了一遍 Linux 記憶體分配的整個鏈路,本文的主題依然是記憶體分配,這一次我們會從微觀的角度來探秘一下 Linux 內核中用于零散小記憶體塊分配的記憶體池 —— slab 分配器。 在本小節中,筆者還是按照以往的風格先帶大家簡單 ......

    uj5u.com 2023-04-05 16:44:11 more