OO: 2.0.0 OS: MS Windows 5.1 (XP Professional) HSQLDB: default embedded version
abbreviations: GUI graphical user interface CUI character-base user interface Thanks for the advice from [EMAIL PROTECTED] and [EMAIL PROTECTED] Additional clarification is needed. 2. Where to find out the documentation of design logic for this additional restriction in OO Base GUI? quote from previous info. provided by Frank ... For determining which row to update/insert in a table, OOo needs to uniquely identify this row ... I would have thought that the enforcement of referential integrity is always the resposibility of the DBMS engine (the backend). GUI and CUI serves mainly to facilitate the communication with the DBMS engine, not to alter the SQL protocol or semantics. Certainly there are DBMS engines shunning the burden of enforcing referential integrity (e.g. MySQL ISAM 4.14) and they shift this burden to users and application software developers. A popular competitive DBMS GUI, the MS Access 2002, does not impose this extra requirement in its GUI design. Adding or updating rows in tables without unique keys can be done in MS Access 2002, in compliance with SQL standards. Is there any fundamental or architectural reason why OO Base GUI could not achieve the same as MS Access 2002? Does anyone know any other DBMS GUI with similar GUI constraint on table design? Can you elaborate the design details if there is indeed other DBMS GUI of similar behavior? some names recalled: MySQL InnoDB, MySQL MaxDB, Firebird, Berkeley DB, PostgreSQL, IBM Cloudscape, McKoi SQL DB (Java), Oracle, SyBase, etc. 3. How to find out the version of HSQLDB engine embedded in an OO Base installation? quote from previous info. provided by Frank ... Note that there are some backends which support data update even without primary keys ... if your backend doesn't support this - and HSQLDB, OOo's default backend doesn't ... Please note the test results in my previous message. The results contradict the above info. Could someone verify my previous test results? I was able to add data to tables without unique keys in OO Base using the default HSQLDB, as long as I do not go through OO Base GUI. 1. How to turn off the requirement of unique key or primary key, as imposed in OO Base GUI, just before saving a newly designed table? Can I still ask for a way in future versions to turn off this behavior in OO Base GUI? I currently consider it as a design flaw in OO Base GUI. Hence I was interested in finding its design logic. In case that the potential user benefit from this GUI constraint eluded me. Thanks for advice. Ray --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
