[horde] Fwd: [turba]: entity relation ship model of turba database

Carsten horde-groupware at familie-lahme.de
Tue Feb 27 07:46:04 UTC 2018

> If the user is to be able to have multiple address books, you MUST  
> use the share system. I.e., 'use_shares' => true in $cfgSources. In  
> that case, as you mention, turba_objects.owner_id is mapped to the  
> share. What you are seeing when the turba_objects.owner_id is the  
> horde username instead of a share_id - this is the user's original,  
> default address book. The reasons for this are  
> historical/backwards-compatibility/flexibility.
> The database tables in Turba, and Horde in general, are not really  
> designed to be accessed from outside applications. For that, you  
> should be using the external API.

Hi all,
I see that some of you pointing out this "API".
Could You point out the documentation about it, too, please?

I have searched a while, but could not locate it.
Even so, I rather talk to my SQL Server than to some other strange  
abstraction layer, it maybe worth to have a look.


More information about the horde mailing list