[horde] Horde 4.0-ALPHA1: table already exists

[Jan Schneider]

Zitat von Michael Rubinsky <mrubinsk at horde.org>:

>
> Quoting Michael M Slusarz <slusarz at horde.org>:
>
>> Quoting Hiromi Kimura <hiromi at tac.tsukuba.ac.jp>:
>>
>>> Quoting Jan Schneider <jan at horde.org>
>>>
>>>> Zitat von Hiromi Kimura <hiromi at tac.tsukuba.ac.jp>:
>>>>
>>>>> Quoting Jan Schneider <jan at horde.org>
>>>>>
>>>>>> Well, for some reason it's trying to create the schema tables,  
>>>>>> even though it should only *update* them if they exist. I can  
>>>>>> only think of permission problems causing this behavior.
>>>>>>
>>>>>> Oh, I only read now that you get this after login not when  
>>>>>> running the schemas? Where do you get the messages? In some log  
>>>>>> file, in a fatal error, in a notification bubble?
>>>>>> Are all schemas green in the configuration screen?
>>>>>
>>>>> Yes, I only see this message once per login.
>>>>> The messages were logged into the log file specified in horde's config.
>>>>> It is not fatal error, it seems working. All schemas are green.
>>>>
>>>> So, these message are still logged, even though the schemas are  
>>>> all installed and green?
>>>
>>> Yes, these messages are still logged even schemas are all  
>>> installed and green,
>>> at every login.
>>>
>>>> That would be perfectly find and the expected behavior.
>>>
>>> Humm..
>>
>> I have also noticed this.  I believe this happens due to the login  
>> task that attempts to do migrations when an admin user logs in.   
>> Very annoying in the log since IIRC migrations don't try to check  
>> for existing tables - they go directly to a create table call.
>
> This is not true, at least not for the tables the migration scripts  
> are creating. Migrations check for table existence before the create  
> call. The schema tables are not checked for first, but is wrapped in  
> a try/catch block that ignores the exception - though thinking this  
> though, I guess Horde_Db still logs the error before throwing the  
> exception. I guess we should check existence of the schema tables  
> first also.

This happened already earlier today.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/