The scripts with the new names will be included with HGW 1.1 or 1.0.4 
if there ever will be a 1.0 release with a newer Turba version.

I've thought for a while that we should keep it as turba_objects 
because that's the table, and you can use turba with other tables. But 
I think it's time to let go of that to make the default install 
easier, so just turba.sql is okay with me.

Question to all developers: should we rename the default schema sql 
script to turba.sql (instead of turba_objects.sql) so that it's picked 
up automatically from the groupware build script? Or is there any 
reason to keep the current name and we should better work around this 
in the build script?

$Horde: horde/scripts/sql/create.mysql.sql,v 1.4.6.10 2007/09/27 
22:36:49 jan Exp $

[I think the description should say: "../sql/groupware.mysql.sql ..."



There is no turba table creation in the script:



"CREATE TABLE turba_objects (

     object_id VARCHAR(32) NOT NULL,

     owner_id VARCHAR(255) NOT NULL,

     object_type VARCHAR(255) NOT NULL DEFAULT 'Object',

     object_uid VARCHAR(255),

     object_members BLOB,

     object_name VARCHAR(255),

     object_alias VARCHAR(32),

     object_email VARCHAR(255),

     object_homeaddress VARCHAR(255),

     object_workaddress VARCHAR(255),

     object_homephone VARCHAR(25),

     object_workphone VARCHAR(25),

     object_cellphone VARCHAR(25),

     object_fax VARCHAR(25),

     object_title VARCHAR(255),

     object_company VARCHAR(255),

     object_notes TEXT,

     object_pgppublickey TEXT,

     object_smimepublickey TEXT,

     object_freebusyurl VARCHAR(255),



     PRIMARY KEY(object_id)

);



CREATE INDEX turba_owner_idx ON turba_objects (owner_id);



GRANT SELECT, INSERT, UPDATE, DELETE ON turba_objects TO horde@localhost;"