C. Bensend wrote: > > >> MySQL schema is closer to >> >> CREATE INDEX "address_firstname_key" ON "address" ( "firstname", >> "lastname"); >> >> Are you sure that those entries need something unique? > > I personally prefer them to be unique, just so my users don't > double up their contacts. It doesn't *have* to be, though. > I just wanted to mention that the recommendation doesn't really > do what I think is intended, as only one user can have a contact > named "Bob Smith". :) > "Robert Smith", "Bob Smith", "Bobby", "Mr. Smith" and "Brad Jr." can be same person. SquirrelMail address book has only one requirement. Unique nickname per address book. Any other restriction is specific to storage backend and might create problems when you change your backend. If unique indexes increase load of your DB, you might consider making them not unique. If users hit artificial restriction in DB, they won't see SquirrelMail address book warning, they will see DB error. Documentation needs fixes. I am not DBA, but I suspect that setting unique 4 key index not required by application is not good thing. Documentation could show several ways to do index stuff. -- View this message in context: http://old.nabble.com/Slight-modification-to-PostgreSQL-address-table-definition-tp29095696p29107643.html Sent from the squirrelmail-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ----- squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@xxxxxxxxxxxxxxxxxxxxx List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
