It works for me.

   public abstract Integer getIntegerField();
   public abstract void setIntegerField(Integer value);

   public abstract int getIntField();
   public abstract void setIntField(int value);


12:30:34,262 DEBUG [Child] Executing SQL: CREATE TABLE CHILD(CHILD_ID BIGINT NOT NULL, name VARCHAR(250) BINARY, integerField INTEGER, intField INTEGER NOT NULL, PARENT_FK BIGINT, CONSTRAINT pk_CHILD PRIMARY KEY (CHILD_ID))


Do you have a testcase?

Thanks,

alex

Ivens Porto wrote:

Hi,

I'm using JBoss 3.2.2 and PostgreSQL 7.3.4.

JBoss is doing something that I can't figure out why.

In my CMP beans, JBoss always use the constraint NOT NULL for fields of
type integer, even thought I don't set the <not-null/> property in
jbosscmp-jdbc.xml for the fields.

If the persistent field in the CMP bean is of type int or Integer, JBoss
creates the database table with the constraint NOT NULL for integer type
fields.

Does anyone knows why JBoss does this?





------------------------------------------------------- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to