The four 700-series errors are due to the table references used in the views - tables that were failed to be created due to a failure within the 'LoadBotsSchema()' procedure.
Those you can ignore because it's understood why the errors are being triggered.
The line 675 error is actually the line in the script that calls the procedure.
I'm pretty certain I know why it's failing..but, not the cause of it.
There are code checks in place to look for existing column names..then, if found, an import is performed.
That's to address different incarnations of bot schema.
For some reason, either the code block criteria is triggering an error, or a false positive is returned and the import is triggering on a non-existent column name.
(Just not sure which atm since I can't replicate the condition.)
EDIT: I'm still looking into alternative code block criteria. In the mean time, I need to write-up how to apply that manually from update failure to end.
__________________
Uleat of Bertoxxulous
Compilin' Dirty
|
Hybrid Mode
