Re: relations between tables

Reinhard Müller <[email protected]> Mon, 04 Mar 2013 09:08:23 +0100
Newsgroups gmane.comp.gnu.enterprise.devel
Message-ID <4973960.lIEeJsJefL@pc01>
--===============3165143567933146039==
Content-Type: multipart/signed; boundary="nextPart2107448.6VCRlNlDFf"; micalg="pgp-sha1"; protocol="application/pgp-signature"
Content-Transfer-Encoding: quoted-printable


--nextPart2107448.6VCRlNlDFf
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"

Dear Theanoula,

Am Sonntag, 3. M=E4rz 2013, 20:48:36 schrieb Theanoula:
> <datasource name=3D"dts_customer" connection=3D"gnue" table=3D"transa=
ctor" />
>=20
> <datasource name=3D"dts_cars" connection=3D"gnue" table=3D"cars"
>  master=3D"dts_customer" masterlink=3D"id" detaillink=3D"customer_id"=
 />
>=20
> <datasource name=3D"dts_contract" connection=3D"gnue" table=3D"contra=
ct"
>  master=3D"dts_cars" masterlink=3D"id" detaillink=3D"car_id" />
>=20
>=20
> I have created the primary and foreign keys in the database.
> When I search(in the form) in dts_customer.name I get all the info I =
need.
> The same happens when I search in dts_cars.car_number(I get everythin=
g) but
> when I search in dts_contract.contract_no I don't get the right info.=


I haven't really worked with gnue-forms much lately (unfortunately), bu=
t IIRC,=20
chained master-detail has some issues in forms.

Having said that, I would suspect that actually this is not a pure line=
ar=20
chained master-detail: isn't the contract the thing that connects custo=
mers=20
and cars? So actually dts_cars is a detail to dts_customer, but dts_con=
tract=20
would also be a detail to dts_customer?

Thinking even more about it: can there be more than one contract per ca=
r? Or=20
wouldn't contract and car be an 1:1 relationship, meaning that you coul=
d put=20
both in the same table?

Just thinking out loud...

Thanks,
Reinhard
--nextPart2107448.6VCRlNlDFf
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iJwEAAECAAYFAlE0VncACgkQKm/Tcod8puPhUwP/Who89ndNOSMMLCay8roSVUdq
gh4EvAEU0iYlfuaBUHYCoFgPKlpadfQdeqB+/q5DNAP1fCLGQuj1f+DeZm6RhCCg
QfpKfzuQToB5H9GSKradl8/ep50/8a4hIdtPOqBLN1H4FNj5ucOm+gsBgqeTBOFC
iYoTgxsiLnD1puAblYI=
=x6/C
-----END PGP SIGNATURE-----

--nextPart2107448.6VCRlNlDFf--



--===============3165143567933146039==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
gnue-dev mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/gnue-dev

--===============3165143567933146039==--