I skipped nothing but executed all queries, continuing on errors with the next one and assumed that if there was an existing record it would be fine already...
Maybe not the best way, but it worked. -- Jan-Albert Jan-Albert van Ree | HPC Specialist | Digital Services MARIN | T +31 317 49 35 48 | j.a.v....@marin.nl<mailto:j.a.v....@marin.nl> | www.marin.nl<http://www.marin.nl> [LinkedIn]<https://www.linkedin.com/company/marin> [YouTube] <http://www.youtube.com/marinmultimedia> [Twitter] <https://twitter.com/MARIN_nieuws> [Facebook] <https://www.facebook.com/marin.wageningen> MARIN news: Courses Hydrodynamics Floating Offshore Structures & Ship design<https://www.marin.nl/courses-hydrodynamics-floating-offshore-structures-and-ship-design> ________________________________ From: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> on behalf of Eckert, Doug <doug.eck...@dowjones.com> Sent: Thursday, March 19, 2020 13:08 To: spacewalk-list@redhat.com Subject: Re: [Spacewalk-list] Spacewalk 2.10 Released! Did you skip the one with the duplicate key constraint error, or did you remove the existing record with the matching key and re-insert?
_______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
