> > Am 29.05.2006 um 08:00 schrieb Tomas Kuliavas: > >>> I have to transfer the user preferences to another mailserver without >>> MySQL support. No access to a database server. I have to convert >>> the BLOBs >>> into plain text files รก la email.prev - how? >>> >>> I know about the scripting, I only want to know how to make those >>> binary >>> BLOBs readable by a human (me or rather the shell). >>> >>> It might be a MySQL question but I already wanted to ask why the SM >>> developers chose to use BLOB instead of TEXT? It makes administrative >>> tasks as setting (and reading) full_name and email_address quite >>> difficult. Or did I miss a clue? >> >> According to documentation email, firstname and lastname fields use >> VARCHAR data type. BLOB is used only for label field. > > What documentation? About the preferences?
sorry, my mistake. Confused address book, preferences and custom address book schemas. > mysql> desc userprefs; > +---------+--------------+------+-----+---------+-------+ > | Field | Type | Null | Key | Default | Extra | > +---------+--------------+------+-----+---------+-------+ > | user | varchar(128) | | PRI | | | > | prefkey | varchar(64) | | PRI | | | > | prefval | blob | | | | | > +---------+--------------+------+-----+---------+-------+ > 3 rows in set (0.00 sec) > > There ist a key (e.g. full_name) and a value as BLOB. > > You may had table address in mind: > > mysql> desc address; > +-----------+--------------+------+-----+---------+-------+ > | Field | Type | Null | Key | Default | Extra | > +-----------+--------------+------+-----+---------+-------+ > | owner | varchar(128) | | PRI | | | > | nickname | varchar(16) | | PRI | | | > | firstname | varchar(128) | | MUL | | | > | lastname | varchar(128) | | | | | > | email | varchar(128) | | | | | > | label | varchar(255) | YES | | NULL | | > +-----------+--------------+------+-----+---------+-------+ > 6 rows in set (0.01 sec) > > 'label' is a VARCHAR. > >> I think reasons are historical. MySQL supports TEXT only since >> 3.21.10. Or >> maybe it was done because TEXT data type is not standard SQL. > > Doesn't have to be TEXT. At the moment I can't think of an option > that requires more than VARCHAR(255). I may be wrong, who knows what > SM wants to store in those BLOBs. Maybe user pictures a the prefered > novel :) user signatures use more than 255 bytes. Theoretically newmail plugin can store custom audio files in SQL. -- Tomas ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 -- squirrelmail-users mailing list Posting Guidelines: http://www.squirrelmail.org/wiki/MailingListPostingGuidelines List Address: [email protected] List Archives: http://news.gmane.org/thread.php?group=gmane.mail.squirrelmail.user List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
