实体类为一对多对多时,如何写submit方法

工作中常常会碰到表关系为一对多对多的情况,看起来略微有些复杂,但是只要思路清晰,还是可以很顺利的理清关系,敲出代码的,以下面我的工作代码为例:

    @PostMapping("/submit")
	@ApiOperationSupport(order = 6)
	@ApiOperation(value = "新增或修改", notes = "传入operationRent")
	public R submit(@Valid @RequestBody OperationRentDTO operationRent) {
		String rentTime = Long.toString(DateUtil.between(operationRent.getStartDate(),operationRent.getEndDate()).toDays());
		operationRent.setRentTime(rentTime);

		operationRent.setRentNumber(BigDecimal.valueOf((int)operationRent.getRentEquipmentList().size()));
		OperationRent operation = BeanUtil.copy(operationRent,OperationRent.class);
		boolean result = operationRentService.saveOrUpdate(operation);
		if (result && !operationRent.getRentEquipmentList().isEmpty()){
			List<RentEquipmentDTO> equipmentDTOList = operationRent.getRentEquipmentList();
			equipmentDTOList.forEach(item -> item.setRentId(operation.getId()));
			List<RentEquipment> equipments = BeanUtil.copy(equipmentDTOList,RentEquipment.class);
			result = rentEquipmentService.saveOrUpdateBatch(equipments);
			for (int i = 0; i < equipmentDTOList.size(); i++) {
				RentEquipment equipment = equipments.get(i);
				if (result && equipmentDTOList.get(i).getEquipmentSourceList().size() > 0){
					equipmentDTOList.get(i).getEquipmentSourceList().forEach(item -> item.setRentEquipmentId(equipment.getId()));
					result = equipmentSourceService.saveOrUpdateBatch(equipmentDTOList.get(i).getEquipmentSourceList());
				}
			}

		}
		return R.status(result);
	}

这是一个submit方法接口,但是主表关联了一张表后又关联了一张表;
这类关系处理逻辑为,先保存最外层主表,然后循环子表,在单个子表中,保存此层数据,再循环最内层子表,