That fixed it!

Thanks
Dave

On 11/16/07, Henning Westerholt <henning.westerholt@1und1.de> wrote:

Hi Dave,

this error was fixed in r3041. It was introduced as part of some adaptions for
the db_berkeley module. Please update to a recent trunk version, and report
if you still have issues.

Cheers,

Henning