On Tue, 6 Mar 2001, David Jencks wrote:
> Some databases, such as firebird/interbase, require that columns used in
> primary keys be defined not null. In order to make JAWS automatic table
> creation useful for such databases, I suggest we add a nullable element to
> JAWS.xml, inside the cmp-field element.
Why don't we instead *always* make the PK fields not null? JAWS
always runs an insert statement with the PK fields present, right? So
this would only cause problems if you failed to populate some of primary
key fields in your ejbCreate, which is a bug anyway IMHO. But if this is
really critical for some reason, you can always create the tables
yourself.
Aaron
