Martin I. Levi dijo:
> Hi Antonio:
>
> Its in our to-do list but we are mostly working on code development
> right now.
I think you can upgrade since there are not too complicated changes. BTW,
I worked without problems with PostgreSQL and RC5. As Thomas suggested
you, I think the problem is related the lack of a sequencer. Take a look
in a simple sequencer table (I don't saw a similar in your posted sample):
CREATE SEQUENCE area_seq
INCREMENT 1 MINVALUE 1 MAXVALUE 2147483647 START 1 CACHE 1;
CREATE TABLE area
(
are_id int4 not null default nextval('area_seq'),
are_name varchar(70) unique not null,
primary key(are_id)
);
-- Default Areas.
INSERT INTO area(are_name) VALUES ('area 1');
INSERT INTO area(are_name) VALUES ('area 2');
INSERT INTO area(are_name) VALUES ('area 3');
This pretty work on PostgreSQL. IN the repository.xml we found:
<class-descriptor class="package.Area" table="AREA">
<field-descriptor name="are_id"
primarykey="true"
nullable="false"
default-fetch="true"
autoincrement="true"
sequence-name="area_seq"
column="ARE_ID"
jdbc-type="INTEGER"/>
<field-descriptor name="are_name" nullable="false"
default-fetch="true"
column="ARE_NAME"
jdbc-type="VARCHAR"/>
</class-descriptor>
And the Area.java Bean is:
public class Area implements java.io.Serializable
{
private Integer are_id;
private String are_name;
}
Please note this is a very trivial sample, in fact we have more
complicated cases in our database. We have a 80 tables and more than 20
SEQUENCES in the DB and it worked fine with OJB RC5 and RC6.
Hope this help.
Best Regards,
Antonio Gallardo.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
