[dev] [cvs] commit: turba/scripts/sql turba_objects.mssql.sql turba_objects.mysql.sql turba_objects.oci8.sql turba_objects.pgsql.sql turba_objects.sql turba/scripts/upgrades 2007-08-05_remove_lastname_null_constraint.sql turba/config attributes.php.dist sources.php.dist

[Michael Rubinsky]

Quoting Chuck Hagenbuch <chuck at horde.org>:

> Quoting Michael Rubinsky <mike at theupstairsroom.com>:
>
>>   - Reorder 'fields' array for the localsql configuration so that
>> 'lastname' is the first field - this assures that contact lists
>> named with a single word will populate the required lastname field.
>
> Doesn't that also mean that when you view the contact list's own
> attributes, the name will be displayed backwards?

Ah. Yes, it does display backwards if your Name Format pref is set to  
'no formatting'.  Silly me only checked with the 'lastname, firstname'  
and 'firstname, lastname' settings.


> I think I finally understand the problem here, it's when you name a
> new contact list, and so you're not using the backend's fields.

Yep, contact list names seem to be stored in the 'name' field - but  
since in our default schema, it's a composite field, it attempts to  
get parsed into a firstname and lastname etc...


What
> about just adding a simple setting to backends named
> "contact_name_field" or some such which specifies which name field (if
> it's not "name") should be used when naming contact lists?

Sure...then just map the 'contact_name_field' back to 'name' when it's  
displayed, right?  Seems simple enough, but I thought we were trying  
to avoid more parameters in the config array though?


Thanks,
mike

--
The Horde Project (www.horde.org)
mrubinsk at horde.org

"Time just hates me. That's why it made me an adult." - Josh Joplin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-keys
Size: 2013 bytes
Desc: PGP Public Key
Url : http://lists.horde.org/archives/dev/attachments/20070806/7d62075c/attachment.bin