Make your own free website on Tripod.com

InstantDB Project
About InstantDB
Project Mail Lists
Short History
Reporting Bugs
Screen Shots
3rd Party Examples
FAQs

Software
Downloads
Documentation
CVS Repositories
Roadmap
License

About Enhydra.org
Who We Are
News, Articles & Events
Getting Involved
Contact Us

Community
Demos
Contributions
Resources
Case Studies
On The Edge! -NEW-
Commercial Vendors


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

InstantDB: Re: Column: null, not found


Clemens

It's possible to get more information out of InstantDB by setting on more
trace bits:

traceFile=./trace.log
traceLevel=1030

This setting should show the parameters being passed into prepared
statements and might highlight if one is missing.

Peter Hearty
Lutris Technologies UK Ltd.
-----Original Message-----
From: Chr. Clemens Lee <clemens@kclee.com>
To: Peter Hearty <peter.hearty@lutris.com>
Cc: rmanuel@perbit.de <rmanuel@perbit.de>; cbregulla@perbit.de
<cbregulla@perbit.de>; clemens.lee@ubsw.com <clemens.lee@ubsw.com>
Date: 06 August 2000 12:55
Subject: Re: Column: null, not found


>Hi Peter,
>
>thanks very much for the reply.
>
>Attached is the trace.log file. I can't see anything except the
>"column: null, not found" exception which shows a column is set to null.
>Do you think dods provides idb with correct values, or is there something
>strange inside instantdb? Can I add specific trace statements to the
>idb code to reveal more detail information?
>
>Thanks for your time,
>   Clemens
>
>Peter Hearty wrote:
>>
>> 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
>
>; Fehlermeldungen references Stammdaten
>e DROP TABLE Fehlermeldungen;
>e create table Fehlermeldungen
>(
>
>    oid DECIMAL(19,0) NOT NULL PRIMARY KEY,
> version INTEGER NOT NULL,
> LastMod Date,
> Benutzer CHAR(20),
>    Linkoid DECIMAL(19,0)  NOT NULL,
> Gemeldet CHAR(30),
> Kontaktart CHAR(10),
> Datum Date,
> Von TimeStamp,
> Bis TimeStamp,
> SYST CHAR(10),
> Release CHAR(10),
> Bereich CHAR(30),
> Modul CHAR(50),
> Prioritaet CHAR(1),
> Fehlerart CHAR(15),
> Bearbeiter CHAR(2),
> Fehlermeldung CHAR(250),
> Fehlerstufe CHAR(2),
> L1Gemeldet Date,
> L1Erledigt Date,
> L1Durch CHAR(2),
> L1Zeit Date,
> L2Gemeldet Date,
> L2Erledigt Date,
> L2Durch CHAR(2),
> L2Zeit Date,
> L3Gemeldet Date,
> L3Erledigt Date,
> L3Durch CHAR(2),
> L3Zeit Date,
> Gesamtzeit Long,
> Loesung CHAR(200),
> LoesungBearbeiter CHAR(2),
> KDInfoam Date,
> Versandam Date,
>        Versandart CHAR(10)
>
>);
>
>e CREATE INDEX I1_Fehlermeldungen ON Fehlermeldungen ( Linkoid );
>e CREATE INDEX I2_Fehlermeldungen ON Fehlermeldungen ( Datum );

-----------------------------------------------------------------------------
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.