Hi Ryo, Harvey
Am Mittwoch, 4. Januar 2006 00:13 schrieb Ryo Chijiiwa:
> One possibility is to add another table with fields like:
> contact_id int,
> field_name text,
> field_type char,
> field_value blob,
> and allow users to add pretty much any kind of data they want. If the
> field_name is somewhat structured (i.e. we know AIM screen names always
> have field_name="AIM") it's pretty easy to extract the data.
That could bite with other contact-sources, for example LDAP.
But LDAP has the ability to have more fields from one type, for example IMs..
So, what about storing more IMs as a serialzed array?
$im[0] = array('type' => 'icq', 'address' => '123446789');
$im[1] = array('type' => 'msn', 'address' => '[EMAIL PROTECTED]');
That stuff goes through "serialze($im)" and the return-val from serialize we
finally can store in the db.
So again, I would like to say to make nothing unique. To avoid double entries
from import, that could be done by modifying the import-function to fit to
our needs.
Karsten
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Ilohamail-devel mailing list
Ilohamail-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ilohamail-devel
