Sorry for reviving this old discussion thread.
I did some search and do not have enough luck yet.
Does anyone recall the issue ID of RFE submitted by Ross Johnson?
Would the RowID feature of JDBC 4.0
bundled in Java 1.6.0 (to be released in 2006)
be sufficiently useful so that the OO Base GUI
no longer needs to impose this unnecessary constraint?
Ray
-----
References:
weblogs.java.net/blog/lancea/archive/2006/03/jdbc_40_rowid_i.html
www.onjava.com/pub/a/onjava/2006/08/02/jjdbc-4-enhancements-in-java-se-6
.html
-----
for casual readers of this discussion thread:
One-to-many relationship is common in DB design.
The one-side table contains primary keys.
The many-side table contains foreign keys.
The many-side table does not require primary keys,
in conformance to SQL standards.
OO Base GUI 2.0.* currently imposes an additional contsraint
that tables with foreign keys require an extra primary key
to allow insertion of new data through GUI.
If we bypass OO Base GUI (losing GUI benefits),
data insertion through OO Base CUI of SQL is OK
for tables with foreign keys and without primary key,
in conformance with SQL standards.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
