Le 16 sept. 04, à 21:14, Thomas Dudziak a écrit :
The beginner's tutorial on the OJB website uses this to introduce you
to OJB.
Is somewhere a specific link to this tuto ?
because i've found :
A full featured ODMG 3.0 compliant API. (See the ODMG Tutorial for an
introduction.)
See JDO
Hello,
We use OJB 1.0.1 with one class per table.
To be simple, we have 3 classes : B extend A, and A have a reference to C.
The C id in A is anonymous.
A have the flag ' determine-extends=false '
In B we could ignore the reference to C, but not the C id (which is
anonymous).
If we put :
Yvon Thoraval wrote:
Is somewhere a specific link to this tuto ?
It's the very first one on the site, called Getting started. You can
find it here:
http://db.apache.org/ojb/docu/getting-started.html
Tom
-
To unsubscribe, e-mail:
Le 17 sept. 04, à 09:07, Thomas Dudziak a écrit :
It's the very first one on the site, called Getting started. You can
find it here:
http://db.apache.org/ojb/docu/getting-started.html
fine, tanxs °;))
Yvon
PGP.sig
Description: =?ISO-8859-1?Q?Ceci_est_une_signature_=E9lectronique_PGP?=
Hi everebody!
I have a Super Class named PessoaVO and a Sub Class named PessoaFisicaVO.
So, I set all the atributtes for PessoaVO and for PessoaFisicaVO in a instance of
PessoaFisicaVO.
When I try to insert:
15:22:10,858 INFO [STDOUT] [org.apache.ojb.broker.accesslayer.JdbcAccessImpl] ERROR:
Hi Fernando,
which version of OJB do you use? Till version 1.0.1 the PK value of the
sub-object was not passed to the super-object. So if you don't use
auto-increment 'true' the PK of the internal created super object (in
your case PessoaVO) will not be set.
Update to 1.0.1 should solve this
Hi Armin, I'm using OJB 1.0rc5.
I'll use an object to reference the 1:1 mapping, because I can't upgrade my
OJB now... I have no time :(
But thanks for your tip! Really thanks for your time!
Hi Fernando,
which version of OJB do you use? Till version 1.0.1 the PK value of the
sub-object was
We have designed all our tables to consistently have a few standard
columns. An optimistic lock col. Called MOD_NUM is one of these cols
(defined as an INT). We do this for intersection tables as well but the
problem is that since we don't have a mapping entry for the table, the
mod_num never
Mickael LEFEVRE wrote:
We use OJB 1.0.1 with one class per table.
To be simple, we have 3 classes : B extend A, and A have a reference to C.
The C id in A is anonymous.
A have the flag ' determine-extends=false '
In B we could ignore the reference to C, but not the C id (which is
anonymous).
If we
