Opened 16 years ago

Last modified 11 months ago

#329 new enhancement

Errors should include database filenames where possible

Reported by: Charlie Hull Owned by: Olly Betts
Priority: normal Milestone: 2.0.0
Component: Backend-Glass Version: git master
Severity: normal Keywords:
Cc: Blocked By:
Blocking: Operating System: All

Description (last modified by Olly Betts)

It would be helpful if database errors reported, where possible, the path and filename they occurred in. Apparently this used to happen in earlier versions, but doesn't now.

Change History (5)

comment:1 by Richard Boulton, 16 years ago

Actually, I don't think it did happen in earlier versions - this was confusion due to a comment I made off-channel to Charlie about some other software.

Anyway - probably the easiest way to implement this would be to implement a "THROW" macro for throwing Xapian exceptions, which added file name and line number information to the exception.

comment:2 by Charlie Hull, 16 years ago

Actually this isn't quite what I meant: I was hoping we'd be able to show which *database* file was causing the error (i.e. 'thing/postlist.baseA'). We've had occasions when a customer has reported a fault, but we don't necessarily know which database file has the problem, and want to transmit the broken one somewhere for further diagnostics.

comment:3 by Olly Betts, 5 years ago

Component: Backend-ChertBackend-Glass
Milestone: 1.5.0
Version: SVN trunkgit master

The Xapian::Error class has a "context" string, which for the remote backend indicates the database - I think we could resolve this by setting this for non-remote DatabaseError too.

comment:4 by Olly Betts, 5 years ago

Description: modified (diff)

comment:5 by Olly Betts, 11 months ago

Milestone: 1.5.02.0.0

Postponing in the interests of getting a new stable release series started. This can probably be backported once done.

Note: See TracTickets for help on using tickets.