java - entitymanager.merge() not behaving as I would expect (Creating a new record rather than updating) -

-

I could not find anything relevant. Based on whether I exported and / or updating bulk, whether the previous record is present based on the data read from the CSV exported or not.

Below are two records two databases, though I want to insert it and then update the same record.

If there is already a record in DB, then it works as expected, just updating the existing line

Before this, I was checking the tap And if only / else to add / update and everything worked well That setter had a lot of redundancy, so I changed it on it. I hope that it will always run the update, but in this event a record is not found, it will create a minimum viable distortion record which is updated later. The update works fine - the problem occurs when no pre-record exists, it creates an additional record

How and how this transaction is being done and why is it committed? I do not understand that the second merge creates a new entry when I pass an object to update it that already exists.

I can do all the things as I would like, but I should understand why it is not as I expected that I have lost a basic concept on merger and transaction?

Here my code is

Pathology Pathology = Gate Pathology (Unit Manager, SlideID, MDCLustring, Collate); If (zero == distortion) {entityManager.getTransaction (). Start (); Deformity = new pathology (); Pathology.setSlideId (slideId); Pathology.setCallType (CALLTYPE); Pathology.setCallBy (mdCallString); EntityManager.merge (deformity); Committed to entityManager.getTransaction (). } EntityManager.getTransaction (). Start (); Pathology.setSample (sample); Pathology.setSlides (slides); Pathology.setLocation (location); Pathology.setCallDx (sampleLevelDx); Pathology.setPatientDx (patientLevelDx); Pathology.setRadiologyReports (radiologyReports); Pathology.setModality (instrument); Pathology.setupdateedon (new date ()); String dtm = lineContainer.get (line container. (-) 1); DateFormat sdf = New Simple Format ("MM / dd / yyyy hh: mm a", Locale.US); Date callout = sdf.parse (dtm); Pathology.setCallDate (callDate); If (mdCallString == colbyCallString) {pathology.setRepresentativeSlideDigitized (currentSlide.get (3)); } EntityManager.merge (Pathology); Committed to entityManager.getTransaction (). Edit: So, everything works like I hope if I run 
  Pathology pathology = gate pathology (unit manager, slide id, MDCLSTR) , Coltai); If (zero == distortion) {entityManager.getTransaction (). Start (); Deformity = new pathology (); Pathology.setSlideId (slideId); Pathology.setCallType (CALLTYPE); Pathology.setCallBy (mdCallString); EntityManager.merge (deformity); Committed to entityManager.getTransaction (). } Pathology = Gate Pathology (Unit Manager, SlideID, MDCelstring, Collate); EntityManager.getTransaction () start () .; Pathology.setSample (sample); Pathology.setSlides (slides); Pathology.setLocation (location); Pathology.setCallDx (sampleLevelDx); Pathology.setPatientDx (patientLevelDx); Pathology.setRadiologyReports (radiologyReports); Pathology.setModality (instrument); Pathology.setupdateedon (new date ()); String dtm = lineContainer.get (line container. (-) 1); DateFormat sdf = New Simple Format ("MM / dd / yyyy hh: mm a", Locale.US); Date callout = sdf.parse (dtm); Pathology.setCallDate (callDate); If (mdCallString == colbyCallString) {pathology.setRepresentativeSlideDigitized (currentSlide.get (3)); } EntityManager.merge (Pathology); Committed to entityManager.getTransaction ().

For the second time, the blank that is being examined after the blocks but I want to avoid the repetition. And about the basic question, what is the difference in pathology variables in two cases, which causes different results? In both cases, they mention the same current record in DB - so why someone moves towards one, while the other makes an update.

Thanks


Comments

Post a Comment

Popular posts from this blog

apache - 504 Gateway Time-out The server didn't respond in time. How to fix it? -

-
Using a form submission on an embedded iframe , the customer downloads a compressed log file Requested. The request was sent to the server, which is the compressed log files, perform some database operations and returns a compressed file. After just 2 minutes, 504 gateway time-out server did not respond timely message on browser net panel How to fix this error? The log files were taking a long time to compress, and timeout was set to 2min The error was fixed by extending the file file: # # timeout: The number of seconds before getting the time out. # # # Timeout 120 timeout 600
Read more

c# - .net WebSocket: CloseOutputAsync vs CloseAsync -

-
We have a working ASP.NET Web API REST service, which is one of the methods of our controller, HTTPTTEX. .) Socket handler code looks something like this ... Public async task socket handler (AspNetWebSocketContext context) {_webSocket = context.WebSocket; ... while (! Cts.IsCancellationRequested) {WebSocketReceiveResult Results = _webSocket.ReceiveAsync (Input Segment, cts.Token) .Result; WebSocketsStateCollusocketState = _webSocket.State; If (result.MessageType == WebSocketMessageType.Close || currentSocketState == WebSocketState.CloseReceived) {// What should I use. CloseAysnc () or. CloseOutputAsync ()? _webSocket.CloseOutputAsync (WebSocketCloseStatus.NormalClosure, "Client Requested", cts.Token). Wait (); } If (currentSocketState == WebSocketState.Open) {...}}} .What is the difference between .CooseAsync () and CloseOutputAysnc ()? I tried both of them and they both seemed to work fine but some difference should be the same they both describe very similar to...
Read more

c++ - How to properly scale qgroupbox title with stylesheet for high resolution display? -

-
I am trying to apply a stylesheet for QGroupBox (QT4.8), which works on the normal screen ( 96 dpi) high resolution screen (Yoga 2 Pro, 3200x1800, 275 dpi, windows 8.1). The following style looks good on the 275 dpi screen, but the top margins on a regular 96 dpi screen are far too big. QGroupBox {border: 1px solid red; Range radius: 7px; Margin-top: 12x; } QGroupBox :: Title {subcontrol-origin: margin; Subcontrol-position: left above; Padding-left: 10px; Padding-right: 10px; } Changing the top-margin has an effect, but I did not get a proper setting which works on both screens. If I shorten the value, the content of the group box overlaps with the title on 275 dpi screen. I was also playing with units "East", "PX", "MX", "PT". Reading the document I would have guessed, "2 X" was the correct solution, which should be scaled with different screen resolutions. Without the stylesheet, the groupbox works well on both screens. ...
Read more