Message-
From: Mick Knutson [mailto:[EMAIL PROTECTED]
Sent: Friday, June 27, 2003 9:32 AM
To: [EMAIL PROTECTED]
Subject: Re: AW: [Xdoclet-user] 1-1 unidirectional relationship issue
Well, as I have been frustrated trying to get this to work, I switched
this
to a 1-1 bi-directional relationsh
Local pMedicalHistory
);
ALLERGIES_TABLE:
=
allergies_id: varchar
medical_history_id_fk: varchar
..more attributes...
MEDICAL_HISTORY_TABLE:
==========
medical_history_id: varchar
user_id_fk: bigint
---
Thanks...
Mick Knutson
---
From: "Ingo Bruell" <[EMAIL P
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Mick,
> I am still having an issue here.
> I have now been working on this for about 3 solid days now. Please help!
>
> I get the Allergies created as well as the MedicalHistory object in the DB,
> but the Allergies does not have a medical_histor
I am still having an issue here.
I have now been working on this for about 3 solid days now. Please help!
I get the Allergies created as well as the MedicalHistory object in the DB,
but the Allergies does not have a medical_history_id_fk so I have no way to
find that Allergies from the Medical Hi
I have set up a 1-1 unidirectional relationship just like the xPetstore, but
it does not seem to work at all. I don't get errors, but the relationship
does not update. I have a MedicalHistoryDto that has an AllergiesDto. I can
populate the Allergies by itself like a standalone bean, but not like
I have set up a 1-1 unidirectional relationship just like the xPetstore, but
it does not seem to work at all. I don't get errors, but the relationship
does not update. I have a MedicalHistoryDto that has an AllergiesDto. I can
populate the Allergies by itself like a standalone bean, but not like
