incorrect duplicates accessing DB from two instances of PT3

[scbrigad]

I am running Idleminer FT on two computers and tracking 6max SNG's on one and FR SNG's on the other at the same buyins. They are both getting thrown in to the same DB on the server, both using auto-import on the Full Tilt Program HHF Dir. with an instance of Idleminer and PT3 running on each machine. The remote PT3 auto-import will occasionally (happened 3 times today) start reporting the files as duplicates. When I stop auto-import and use the manual import it loads them in to the DB just fine, and restarting auto-import the glitch seems to go away at least temporarily...

More of an annoyance than anything but I figured I'd report it. Idleminer should have nothing to do with it since its using the main Full Tilt hand history files to auto-import.

[WhiteRider]

It is not safe to import into the same database from two PT3 sources at once, so this could cause problems.
The safest ways to do this are to either have one PT3 instance access the other PC and import all the hands, or wait until after the session on one PC and do a manual import.

[scbrigad]

what have you heard/seen happen that is not safe beyond an occassional crash or this duplicates issue I mentioned? So far this setup has been working pretty well for me, but I don't know if I should be worried about corrupting my DB. Isn't the whole idea of SQL having simultaneous reads/writes hitting the same DB?

[WhiteRider]

I don't know what the details are, I'm afraid, but I'm sure I remember Josh saying that it's not guarenteed safe. I'm sure most of the time it will work fine, but you can't be sure what is happening in the background.