Ticket #1332930 (Feature Requests)

Martin Marques martin at bugs.unl.edu.ar
Sat Aug 12 18:33:13 CEST 2006

On Fri, 11 Aug 2006 15:31:33 -0400, Jason Dixon <jason at dixongroup.net> wrote:
> On Aug 11, 2006, at 2:08 PM, Michel Moreira wrote:
>> --See the DB Structure: http://img61.imageshack.us/my.php?
>> image=erdmb5.jpg
> No offense, but given the design criteria Thomas mentioned earlier
> (iCal-like), doesn't it make more sense to use a "free field"
> method?  That is, to create a single table of "contact" key/value
> pairs associated with the user id?  Then you can easily pull all
> pairs associated with the user and arrange them according to a known
> set of keys (first_name, last_name, email, phone, im_contact, etc).

I'm lost. Wasn't that what he showed? Or am I not understanding your point?

What we need is this:

1) Table with all the posible options for one contact (names, email,  phone number, address, web page, etc.). Each of these options would be a registered row of this table.
2) Table with the contacts of a RC user. Very simple table that identifies a conetact. All the data for this user would go in the table explained in (3) with a reference to the PK of this table.
3) Table with the actual information. For each piece of info of the contaact, there would be a row, with a field referencing to the contract mentioned in (2), the type of option as mentioned in (1) and the value.

That's how I see it. Coments about it?

Lic. Martín Marqués         |   SELECT 'mmarques' || 
Centro de Telemática        |       '@' || 'unl.edu.ar';
Universidad Nacional        |   DBA, Programador, 
    del Litoral             |   Administrador

More information about the Dev mailing list