Avril, I'm not familiar with OJB, but I'm using mysql and nullable columns work just fine when you specify 'required=false' (or leave the attribute out entirely) in your project-schema.xml. It sounds like it may be a DB2-specific issue.
Sorry I can't offer more help, Derek ----- Original Message ----- From: "Avril Kotzen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, July 17, 2002 2:56 AM Subject: Allowing database columns to be nullable > Hi > > I am using OJB 0.9.2. This uses Torque to create the database tables. > I am using a DB2 database. After several modifications to > sql\base\db2 and adding a sql\load\db2 I have managed to create and > populate the tables. However I notice that all columns are defined > with the NOT NULL attribute. This is the case even if "required=false" > is specified or the required attribute is omitted. What do I need to > do so that the NOT NULL attribute is only generated on a need to have > basis. > > I see that although Torque supports DB2 it is untested. Are there any > plans to test it? > > Thanks for your help > Avril > _______________________________________________________________ > http://www.webmail.co.za the South-African free email service > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
