-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SQL error on first re-import of eddblink
#180
Comments
I don't know what is causing your problem. Until this is fixed, you can use |
Wasn't that the problem with the moving fleet carriers? |
I have some verbose debug output that identifies a special case of data that seems to break Trade Dangerous with this exact error.
Checking INARA, The Gnosis has a permanent route through HIP 17862 but appears to be at Epsilon Indi at the time of this comment. This suggests that the error will crop up around every Thursday. Edit: Looks like it'll happen more often. Had this error come up yesterday or so:
Edit 2: Another one of these events, another moving station other than fleet carrier
|
I think this may end up being a consistency issue from my still using the same database from a month or so ago so some interim updates messed it up. However, every time I run the eddblink import the first execution will fail with the following error. The only time it hasn't done that was when I updated again within 24 hours or so.
The second execution will skip that step I'm guessing and work fine, at least insofar as not hitting this integrity error.
The text was updated successfully, but these errors were encountered: