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]

Re: InstantDB: Println's in DatabaseMetaData.getColumns for v3.21


Ahhh ... now I see.  Thanks for the answer.  It through me for a loop,
since the .prp file didn't change, and this only started happening when
I switched from 3.20b1 to 3.21.  Thanks again for the help!

Bill Graham

Peter Hearty wrote:
> 
> Bill
> 
> Sometimes InstantDB uses internal mechanisms to generate meta data and
> sometimes it just uses SQL to query system tables. When it uses SQL, this
> will get logged just like any other SQL. That's what's happening below. You
> can suppress this (and all other SQL logging) using
> 
> SET EXPORT "null" TRACE 0;
> 
> or by setting traceLevel=0 in the .prp file.
-----------------------------------------------------------------------------
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.