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

As I see it you are right, but testing a smaller example yesterday didn't give
me the same result as Christine's. I also
tested the "Fehlermeldung = Update CD (PI)rtddrt" where a error message is set =
a keyword,
I don't know what should have been made with the assignment, but idb don't like
it and I can't find any SQL syntax that looks
like it. Still these things don't give the output that Christine reported, but I
think I have seen the same output before.
Try breaking the statement into small  pieces, it could help locate where the
error(s) are that results in the error report from idb.
I'm sure it's in the statement and not in idb.

Regards
Martin





"Bill Karwin" <bill.karwin@lutris.com> on 18-07-2000 18:32:26

Please respond to instantDB@enhydra.org

To:   instantDB@enhydra.org
cc:
Subject:  Re: InstantDB: Error message "Column null not found"



> Christine Bregulla wrote:

Hi Christine,

> update ...
> Gemeldet =  ,  Modul =  ,

These assignments are not standard SQL syntax, using an empty expression
like this.  This could be the null that the error is directing you to,
not the literal NULL keyword that you assigned to other fields.

Peter, if this is the case, can you consider changing the relevant error
message to  something such as, "Column [blank] not found" or, "Column
[empty] not found"?

> Loesung = in Trossingen upgegradet,

This is also nonstandard SQL syntax.  I'm not sure if InstantDB permits
unquoted string literals.

> LoesungDatum = 2000-02-25 , LoesungZeit = 1970-01-01 ,
> LastMod = 2000-07-01 , Bis = 2000-02-25 ,
> Von = 2000-02-25

Likewise, these date literals are not quoted.  So they appear like
arithmetic expressions.  2000 -2 -25 yields a result of integer 1973,
right?  <g>
I'm not sure if InstantDB permits unquoted date literals.

> Do you know about this and if so, what can we do to avoid the problem.

Without having tried it myself, I can speculate that you should:
- Specify a non-empty expression in assignments to Gemeldet and Modul
- List string literal 'in Trossingen upgegradet' with single-quotes
- List date literals with single-quotes

Regards,
Bill Karwin
-----------------------------------------------------------------------------
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.






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