[dev] [cvs] commit: turba/scripts/upgrades 2.1_to_2.2_sql_schema.php

Jan Schneider jan at horde.org
Mon Dec 3 18:57:11 UTC 2007


Zitat von Michael Rubinsky <mike at theupstairsroom.com>:

> Quoting Jan Schneider <jan at horde.org>:
>
>> Zitat von Michael Rubinsky <mike at theupstairsroom.com>:
>>
>>> mrubinsk    2007-12-03 13:42:11 EST
>>>
>>>  Modified files:
>>>    scripts/upgrades     2.1_to_2.2_sql_schema.php
>>>  Log:
>>>  mdb2 -> db
>>>
>>>  Revision  Changes    Path
>>>  1.16      +9 -10     turba/scripts/upgrades/2.1_to_2.2_sql_schema.php
>>>
>>>  Chora Links:
>>>
>>>
> http://cvs.horde.org/diff.php/turba/scripts/upgrades/2.1_to_2.2_sql_schema.php?r1=1.15&r2=1.16&ty=u
>>
>> The execute() calls don't look quite correct.
>
> Why?
>
> Tested fine with my old turba data. Pear dcoumentation shows it as:
>
> DB_common::execute()
>
> mixed &execute (resource $stmt [, mixed $data = array()])
>
> Where $stmt is a resource returned from DB_common::prepare();
>
> in our code, $insert is the resource returned from $db->prepare()
>
> or am I missing something else really obvious?

Ah, right, sure. My fault.

Jan.

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



More information about the dev mailing list