[Babase] preg upload creates error in cycstats
kfenn
kfenn at princeton.edu
Tue Jan 29 14:27:31 EST 2008
Karl O. Pinc wrote:
>>>
>>> The thing to do is delete the CYCSTATS row that's causing the
>>> problem, fix things, and then rebuild CYCSTATS. That'd be
>>> how I'd try approaching it.
>>>
>>> If you wanted to be brutal, you could delete _all_ the CYCSTATS rows.
>>> Rebuilding will rebuild them anyhow.
>>>
>> I'm chicken to do the whole thing, though that makes the most sense.
>> I'm just going to start by deleting the cpids that are giving me the
>> error.
I'm not chicken about deleting the table anymore now that I realize that
EVERY single automatic mdate from the last cycles update creates the
same error for cpids and cpide values in CYCSTATS...and I'm not
correcting these hundreds of errors manually.
So....I'm deleting CYCSTATS in babase_test and will rebuilt it after I
am done with the update. For anyone who may be using it in babase_test
for some reason: Please go work in babase instead.
This does raise a question of whether I should make this deletion part
of the update protocol. If so, its got to be Step 1 for the update and
I will have to send out an email every six months telling people
CYCSTATS is out of commission until I get the update done. I don't
think this is a big deal as long as I can do a trial update in another
database first....but I have the sense that eventually we are getting
rid of babase_test, right? Its just that working out all the errors
using the babase database could take a while and CYCSTATS would be out
of commission during that time.
The other option would be to have it update automatically. Karl, what
was the original reason for not having an automatic update?
Tabby
--
Tabby Fenn
Research Assistant
Dept of Ecology and Evolutionary Biology
401 Guyot Hall
Princeton University
Princeton, NJ 08544
609 258-6898 (Ph)
609 258-2712 (Fx)
More information about the Babase
mailing list