Could you please send/submit the patch to XDoclet project? Thank you!
Ivens Porto wrote:
Alexey Loubyansky wrote:
You are trying to use uknown and 'known' primary keys at the same time.
You must use either one. Just remove unknown-pk.
Yes, you need to use jdbc-type/sql-type in key-field.
Alexe
Alexey Loubyansky wrote:
>
> You are trying to use uknown and 'known' primary keys at the same time.
> You must use either one. Just remove unknown-pk.
> Yes, you need to use jdbc-type/sql-type in key-field.
>
Alexey, thanks for you help, I did what you recommended and it works
now.
I also modi
You are trying to use uknown and 'known' primary keys at the same time.
You must use either one. Just remove unknown-pk.
Yes, you need to use jdbc-type/sql-type in key-field.
Ivens Porto wrote:
Alexey Loubyansky wrote:
Yes, it should. It is not yet clear for me how the fk field accord to be
non
Alexey Loubyansky wrote:
>
> Yes, it should. It is not yet clear for me how the fk field accord to be
> non-null. All fk fields allow null values by default. Perhaps, it came
> from sql-type? Could you, please, post the declaration of the unknown pk
> from your DDs?
Below is the declaration of my
"accord" should be read "occured" ;)
Alexey Loubyansky wrote:
Yes, it should. It is not yet clear for me how the fk field accord to be
non-null. All fk fields allow null values by default. Perhaps, it came
from sql-type? Could you, please, post the declaration of the unknown pk
from your DDs?
Yes, it should. It is not yet clear for me how the fk field accord to be
non-null. All fk fields allow null values by default. Perhaps, it came
from sql-type? Could you, please, post the declaration of the unknown pk
from your DDs?
Ivens Porto wrote:
Alexey Loubyansky wrote:
It works for me.
Alexey Loubyansky wrote:
>
> 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:
1:48
Please respond to jboss-user
To: [EMAIL PROTECTED]
cc:
Subject: [JBoss-user] PostgreSQL and NOT NULL integer
fields
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,
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
- Original Message -
From: "Ivens Porto" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, October 23, 2003 10:48 PM
Subject: [JBoss-user] PostgreSQL and NOT NULL integer fields
> Hi,
>
> I'm using JBoss 3.2.2 and PostgreSQL 7.3.4.
>
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 property in
jbosscmp-jdbc.xml for the fields.
If the persistent field in the
11 matches
Mail list logo
