Re: iggy annotation shows error messages in content

On Tue, Jun 15, 2004 at 12:47:38PM -0400, Eric Prud'hommeaux wrote:
> On Sat, Jun 12, 2004 at 02:38:04AM -0400, Eric Prud'hommeaux wrote:
> > On Fri, Jun 11, 2004 at 11:04:56AM -0400, Marja-Riitta Koivunen wrote:
> > > Eric,
> > > 
> > > I think iggy did not yet get back to the earlier nicely working state:
> > > 
> > > - Amaya 8.5 on windows
> > > I can create an annotation to iggy.
> > > I cannot load the annotations from iggy but I can from annotest
> > > 
> > > - new Amaya 8.6 in swada (may have errors too)
> > > First: cannot load even annotest annotations if iggy is on the list 
> > > (complaining about failing to load the annotation index)
> > > if I take iggy away from get servers I can load the annotest annotations
> > > Second: now all the sudden I can see an iggy annotation in swada hopefully 
> > > with some interesting errors as content.
> > > 
> > > I'll send a png image as I cannot copy the text easily to my computer.
> > > 
> > > Marja
> > 
> > 2004-06-12T04:11:12Z <ericP> iggy shoudl be a bit more opperational now
> > 2004-06-12T04:11:50Z <ericP> have fixed bugs that keep it from working when retrieving annotations with no authentication
> > 2004-06-12T04:12:01Z <ericP> now to fix the fact that they have no authentication
> > 2004-06-12T04:12:09Z <ericP> (really, that it threw it away)
> > 2004-06-12T06:37:37Z <ericP> done, seems to work for simple tests
> > 
> > give it a shot
> 
> this failure left behind one screwed up entry. i fixed it for now, but
> will restore its broken state later for improving failure handling.
> 
> SQL patch:
> update __AttrLists__ set a=538 where id=584;
> 
> restore bug:
> update __AttrLists__ set a=546 where id=584;
> to restore
> mysql> select * from __AttrLists__ where listId=540;
> +-----+--------+-----+
> | id  | listId | a   |
> +-----+--------+-----+
> | 584 |    540 | 546 |
> +-----+--------+-----+
> 
> that should be the only one like it:
> mysql> select * from __AttrLists__ left outer join __Attributions__ on a=__Attributions__.id where __Attributions__.id is null;
> +-----+--------+-----+------+------+------+------+----------+---------+
> | id  | listId | a   | id   | type | doc  | auth | modified | created |
> +-----+--------+-----+------+------+------+------+----------+---------+
> | 584 |    540 | 546 | NULL | NULL | NULL | NULL |     NULL |    NULL |
> +-----+--------+-----+------+------+------+------+----------+---------+
> 1 row in set (0.01 sec)

I updated two server modules (W3C::Rdf::{SqlDB,ResultSet}) to handle
inconsistent data in the database. I tested this fix by restoring that
annotation to the previous incorrect attribution. Testing in the HTML
interface [1] shows the exciting new bit of fault tolleance:

error:

Can't call method "isa" on an undefined value

It could do with some more context, but at least you get the other
annotations for that page.

[1] http://iggy.w3.org/annotations?w3c_annotation=&w3c_body=&w3c_annotates=http%3A%2F%2Fwww.w3.org%2F2001%2FAnnotea%2FPress.html&w3c_replyTree=&w3c_algaeQuery=&w3c_submit=query+RDF+DB
-- 
-eric

office: +81.466.49.1170 W3C, Keio Research Institute at SFC,
                        Shonan Fujisawa Campus, Keio University,
                        5322 Endo, Fujisawa, Kanagawa 252-8520
                        JAPAN
        +1.617.258.5741 NE43-344, MIT, Cambridge, MA 02144 USA
cell:   +1.857.222.5741 (does not work in Asia)

(eric@w3.org)
Feel free to forward this message to any list for any purpose other than
email address distribution.