[Typo3-dev] fe_user - tt_address 1:m or m:m

[Elmar Hinz]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello frontend developers,

comming back to fe_user and tt_address again, I would like to hear your
advice on a common usage by extensions.

Different models are in use:

* 1:1

sr_feuserregister stores address data into fe_user itself. No relation
to tt_address. Every user gets exactly 1 address this way.

Please list extension that use the 1:1 model here:

- -
- -
- -

* 1:m

Every user can get several adresses of different type this way (home,
home2, postatl, holyday, etc.). This model is more compatibel with the
kind that email programms store and exchange contacts. (vCard, .vcf)

Every address belongs to one user.


Please list extension that use the 1:m model here:

- -
- -
- -



* m:m

In real life there are often addresses, that belong to different people,
i.e. the delivery address of a company, the home adrress of a family. I
think this model is not very common. But it would be consequent from the
philisophy of database normalization.

There is a clear disadvantage. If you import .vcf from several people
with the same postal address for example, you need a tool to connect
them to the same tt_address postal dataset. They give you a single one
for each person. That probably needs to be conntrolled by hand.


Please list extension that use the m:m model here:

- -
- -
- -



Now, what do you think could be THE COMMON MODEL for extensions.

What model should find its way into Project Coding Guidelines?

Regards

Elmar


- --
Climate change 2005: Mexico, Guatemala, New Orleans, Sahel, Bangladesh,
Spain, Portugal, Austria, Swiss, France, ...
Production of CO2 is killing people.
Production of CO2 just for fun is killing people just for fun.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDkrr2O976RNoy/18RArrMAJ9R1cnEHBaTNtGmsE8jEdWaOzPRUACgiMZH
WYCCCN0sUP4tPVorENmOht4=
=qqB6
-----END PGP SIGNATURE-----