Thanks Kelvin ; )(again) Adriano Crestani
On 4/4/07, Kevin Williams <[EMAIL PROTECTED]> wrote:
Hello Adriano, This use of convention is actually for the "write" side of things. A PK is needed to generate correct update commands based on the SDO Change Summary. In the absence of a defined PK, the DAS will assume any column named ID is the PK and use that in the generated statement. Also, we have tried to avoid dependence on Database Schema metadata for information such as PKs and FKs. The reason for this is that they are sometimes not defined in the database. Thanks, --Kevin Adriano Crestani wrote: > I was wondering why the "id" field being mapped as a table PK is > defined as > "Convention Over Configuration". Because in java it is possible to > retrieve > the table PK only using java.sql.DatabaseMetaData.getPrimaryKeys(String > catalog, String schema, String table) method. > > Does the "id" Convention Over Configuration exist only because some DBMS > does not support the java.sql.DatabaseMetaData.getPrimaryKeys(String > catalog, String schema, String table) method? > > Adriano Crestani > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
