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

Hi,

we had some problems concerning table constraints and schema
alteration statements using release 3_25 (so I don't know whether
they have been solved in the meantime):

- adding a column with an alter table would sometimes corrupt
the data.

- sometimes an alter table  would  not be  accepted, especially
if there have been alter table statements before.

- if the prp file is empty the result set resulting from a call to
 methods getPrimaryKeys() and getImportedKeys()
is null. Also, table constraints like unique(col1, col2) or
primary key (col1, col2) are not enforced in this case.

- if the prp file consists only of  the line  "relativeToProperties=1"
you get an sql error when trying to connect to the database. In
former releases such a prp file was possible.

Besides, it would be fine if table constraints were not only
addable but droppable as well.

Cheers
Otto







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