Normally I'd agree, but we haven't quite made a final database
decision. We're also finding that it's very convenient to do initial unit
test on the developer's PC with hypersonic, then move to our development
server with a heavier-duty dbms.
Autogeneration means I can put off generating table definitions (which we
do in xsl) and hopefully avoid generating different sql for different
databases...
This seems like a pretty basic capability, and there's already provision in
the individual database schema (null=, not-null=) files, so I'm hoping
it's there somewhere.
Kirk Yarina
At 07:46 PM 9/19/00 -0400, you wrote:
>The best way not to use tables autogeneration at all
>Make optimal schema, write table api beans for your schema, write
>application beans
>
>
>----- Original Message -----
>From: "KirkYarina" <[EMAIL PROTECTED]>
>To: "Orion-Interest" <[EMAIL PROTECTED]>
>Sent: Tuesday, September 19, 2000 12:33 PM
>Subject: NULL/NOT NULL with autocreated tables
>
>
> > I'm using orion-ejb-jar.xml to define many of the characteristics of our
> > applications database table fields, and am unable to determine how I can
> > specify NULL/NOT NULL constraints for these fields. I rtfm (such as it
> > is....) and looked at the orion-ejb-jar dtd, and couldn't find an answer.
> >
> > We're switching between several DBMS's during development, using different
> > databases for different programmers and tasks, and still tweaking the
> > schema a bit. It's convenient to let Orion automatically create tables
> > while all this is going on but I need to be able to control whether null
> > fields are allowed, and have been unable to figure out how to do so. Can
> > anyone help?
> >
> > Thanks!
Kirk Yarina
[EMAIL PROTECTED]
