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: Some InstantDB questions


Hi Michael,
 
Yes I did get a response from Peter Hearty.  He always responds quickly to questions and bug reports.
 
I am not sure if it went to the whole group and I seem to have deleted it. Peter was able to reproduce #1 and will fix it.  #2 involves a misunderstanding of the command on my part.  He agrees with #3.  He will address #4 in a future release.
 
The InstantDB source code will be released under an open source arrangement. The new licensing terms require no fees even for commercial use.
----- Original Message -----
Sent: Saturday, April 22, 2000 1:02 PM
Subject: InstantDB: re: Some InstantDB questions

Tony -
 
I've no exposure at all to InstantDB, but your item #1 kind of transfixed me. Is this database really ok to use? I also didn't see a response to your query, or was it done off the list?

Michael Simcich
AccessTools

 
Tony wrote:
 
We are very please with InstantDB at Captura Software in Seattle, but we
have a few questions to throw out:

1. When Auto Increment is on, the column gets incremented not only when a
new row is inserted but also every time a row is updated.  I can't imagine
why anyone would want to increment on an update.  Although this can be fixed
by turning auto-increment off temporarily with a SET command, it seems like
a bug.

2. The command SET INCREMENT_BASE MAX does not change the Auto Increment
value although SET INCREMENT_BASE 5000 works fine.

3. You can get the last value inserted for an Auto Increment column by
calling the method GetLastValueInserted but this fact is not documented in
the prose on Auto Increment

4.  The datatype of DATE causes problems with Borland's Data Express
package.  It thinks the column only holds a date rather than a date and a
time.  If InstantDB had an alias of DATETIME for the DATE type, it is
probable that Data Express (and DB Visualizer) would not drop the time part
of the field.

We would appreciate any feedback from the InstantDB team or from other
users.


Tony Marshall
(425) 424 1176 Office
(206) 898 0597 Mobile