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

Bill

Yes - I;m gradually working my way through the bug list. The meta data
problems are being fixed and I'm hoping to get a beta out this week.

As to the VARCHAR/TEXT thing. Yes that's a reasonable point. It's kind of
ended up this way for historical reasons. Let me have a little think about
the implications of this.

Regards

Peter Hearty
Lutris Technologies UK Ltd.
-----Original Message-----
From: BSmith@ixl.com <BSmith@ixl.com>
To: instantDB@enhydra.org <instantDB@enhydra.org>
Date: 07 July 2000 19:06
Subject: RE: InstantDB: DatabaseMetaData Support


>Hi Peter,
>
>I was wondering if you all had made any progress on this. For what I'm
doing
>now it's not critical since I can manage the creation of tables, etc.
>through Toplink. On larger scale projects, this could get cumbersome.
>
>Also, is there a commercial RDBMS that Instantdb is most similar to as far
>as DDL? Toplink wants a specific DB selected (Oracle, Informix, etc.) for
>performing DDL (even though it uses JDBC calls for the bulk of the work).
So
>far, I've selected Informix and it seems to work ok.
>
>Lastly, on another thread, somebody was talking about CHAR(256) and how
much
>space it takes. This sounds like a VARCHAR to me, but is mapped to a CHAR
in
>the Instantdb documentation. It sounds like a VARCHAR would be better
mapped
>to a TEXT (BINARY).  What are your thoughts as to this being a good or bad
>idea? Is the only cost a little bit of performance for using TEXT?
>
>TIA,
>Bill
>
>-----Original Message-----
>From: Peter Hearty [mailto:peter.hearty@lutris.com]
>Sent: Friday, June 30, 2000 10:41 AM
>To: instantDB@enhydra.org
>Subject: Re: InstantDB: DatabaseMetaData Support
>
>
>Bill
>
>Sounds like a bug. I'll look into it.
>
>Regards
>
>Peter Hearty
>Lutris Technologies UK Ltd.
>-----Original Message-----
>From: BSmith@ixl.com <BSmith@ixl.com>
>To: instantDB@enhydra.org <instantDB@enhydra.org>
>Date: 30 June 2000 15:25
>Subject: RE: InstantDB: DatabaseMetaData Support
>
>
>>Peter,
>>
>>I noticed when I call the getTables() method and pass it as the last
>>argument an array of strings of the types,
>>if I use "TABLES" as reported by getTableTypes, I get no matches. If I use
>>"TABLE" it returns my tables. Is this
>>the correct functionality or should getTableTypes return "TABLE" instead
of
>>"TABLES"?
>>
>>TIA,
>>Bill
>>
>>-----Original Message-----
>>From: Peter Hearty [mailto:peter.hearty@lutris.com]
>>Sent: Friday, June 30, 2000 9:56 AM
>>To: instantDB@enhydra.org
>>Subject: Re: InstantDB: DatabaseMetaData Support
>>
>>
>>Bill
>>
>>Only some of the calls you need are actually supported, and some are only
>>partially supported.
>>
>>getTables(...) fully supported
>>getCatalogs(...) always returns an empty result set
>>getTableTypes(...) always returns a single row with 'TABLES' as its value
>>getPrimaryKeys(...) - partially supported - key sequence is incorrect
>>getImportedKeys(...) always returns an empty results set
>>
>>Regards
>>
>>Peter Hearty
>>Lutris Technologies UK Ltd.
>>-----Original Message-----
>>From: BSmith@ixl.com <BSmith@ixl.com>
>>To: instantdb@enhydra.org <instantdb@enhydra.org>
>>Date: 29 June 2000 22:29
>>Subject: InstantDB: DatabaseMetaData Support
>>
>>
>>>I'm using a product (Toplink for Java) that requires that the following
>>>methods are supported in the DatabaseMetaData interface. In the InstantDB
>>>JDBC implementation are the following methods all supported?
>>>
>>>getTables(...)
>>>getCatalogs(...)
>>>getTableTypes(...)
>>>getPrimaryKeys(...)
>>>getImportedKeys(...)
>>>
>>>TIA,
>>>Bill
>>>
>>>
>>>=====================
>>>Bill Smith
>>>Senior Software Engineer
>>>iXL, Inc.
>>>4600 Cox Rd.
>>>Glen Allen, VA 23060
>>>
>>>tel: 804.217.8888
>>>fax: 804.217.8890
>>>bsmith@ixl.com
>>>
>>>This message is intended only for the use of the Addressee and may
contain
>>>information that is PRIVILEGED and CONFIDENTIAL. If you are not the
>>intended
>>>recipient, dissemination of this communication is prohibited. If you have
>>>received this communication in error, please erase all copies of the
>>message
>>>and its attachments and notify us immediately.
>>>
>>>
>>>-------------------------------------------------------------------------
-
>-
>>--
>>>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.
>>--------------------------------------------------------------------------
-
>--
>>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.
>---------------------------------------------------------------------------
--
>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.