Clemens
My best guess is that one of the parameters in the PreparedStatement is not
getting set. Try setting
traceFile=./trace.log
traceLevel=6
in the database .prp file and having a look at trace.log. If one of the
parameters is null it ought to
show up there.
Regards
Peter Hearty
Lutris Technologies UK Ltd.
-----Original Message-----
From: Chr. Clemens Lee <clemens@kclee.com>
To: peter.hearty@lutris.com <peter.hearty@lutris.com>
Cc: clemens.lee@ubsw.com <clemens.lee@ubsw.com>; rmanuel@perbit.de
<rmanuel@perbit.de>; cbregulla@perbit.de <cbregulla@perbit.de>
Date: 01 August 2000 13:54
Subject: Column: null, not found
Hi Peter,
we are developing an online support system with Enhydra and
InstantDB.
As a middle layer we use Enhydra´s Dods.
Unfortunately we are stuck at a hard to find bug:
"Column: null, not found"
We are not sure if the problem is in our code, in the dods
layer, in instantdb, or somewhere in between. Also, the
amount of information we can provide you might be a little
bit overwhelming, as we have not much inside knowledge into
dods and instantdb. But maybe you can give us a hint how to
provide you (or someone else ) with more specific debug
messages.
If I could provide you with a smaller test case, I would
happily create one. Meanwhile, the debug output might give
you already an idea, what is going wrong.
-----------------------------------------------------------------------------
To unsubscribe from this mailing list, send email to majordomo@enhydra.org
with the text "unsubscribe instantdb" in the body of the email.
If you have other questions regarding this mailing list, send email to
the list admin at owner-instantdb@enhydra.org.
|