 | | DB errors in set database —Ray Sanders
|
| | | I've been seeing errors from the guide set database. So far I have seen this on three sets: 1374, 7104 & 7000. I noted it over in admin.general, but I don't think that caused any fixes to occur. (...) It only occurs on certain sets, but it occurs (...) (21 years ago, 2-Nov-03, to lugnet.admin.database)
|
| | | |
| | | | | Re: DB errors in set database —David Eaton
|
| | | | (...) Add 10026 to the list... (URL) I didn't have any issues with 7000... DaveE (21 years ago, 3-Nov-03, to lugnet.admin.database)
|
| | | | |
| | | | | | Re: DB errors in set database —Ray Sanders
|
| | | | (...) Oddly 7000 causes the error for me, but 10026 does not. Perhaps the error is related to who has what sets listed in thier own inventory ? (as I have the 3 I reported, but not 10026) Ray (21 years ago, 5-Nov-03, to lugnet.admin.database)
|
| | | | |
| | | | | | Re: DB errors in set database —David Eaton
|
| | | | (...) ! I actually had all 4 sets in question, but 7000 didn't cause an error. However, now I don't get the error at all! Maybe it's been fixed! DaveE (21 years ago, 5-Nov-03, to lugnet.admin.database)
|
| | | | |
| | | | | | Re: DB errors in set database — Todd Lehman
|
| | | | (...) I ran a script a couple days ago which did a thorough internal consistency check of the data and it found some anomalies, which it then fixed. --Todd (21 years ago, 6-Nov-03, to lugnet.admin.database)
|
| | | | |
| | | | | | Re: DB errors in set database —Ray Sanders
|
| | | | (...) All the ones I reported appear to be fixed. Thanks Todd :) Ray (21 years ago, 6-Nov-03, to lugnet.admin.database)
|
| | | | |
