[Dbix-class] update oracle clob field fails

[Marc Logghe]

On Thu, Feb 23, 2012 at 4:37 PM, Marc Logghe <logghe.marc at gmail.com> wrote:

> On Thu, Feb 23, 2012 at 4:19 PM, Marc Logghe <logghe.marc at gmail.com>wrote:
>
>>
>>
>> On Thu, Feb 23, 2012 at 4:15 PM, Peter Rabbitson <rabbit+dbic at rabbit.us>=
wrote:
>>
>>> Which version of DBIC is this?
>>>
>>>
>>> Hi Peter,
>> it's still version 0.08192, guess time for an upgrade ...
>>
>
> OK, upgrade seems to have fixed that weird update statement, now it looks
> like expected:
> UPDATE anncomment SET comment_text =3D ? WHERE ( anncomment_id =3D ? )
> Apologies for not upgrading first, before poking the list.
>
> Still have an exception unfortunately:
> DBI Exception: DBD::Oracle::st execute failed: ORA-04043: object
> anncomment does not exist (DBD SUCCESS: OCIDescribeAny(view)/LOB refetch)
> However, the row with the corresponding anncomment_id is definately in the
> database. I'm digging further.
>
> Thanks !
>
> Not sure if this is a feature or a bug.
The update is going fine when the table name is fully qualified (e.g.
prefixed by user/schema):
#__PACKAGE__->table("anncomment");
__PACKAGE__->table("biosql.anncomment");

Is it possible that DBIC is not (implicitely) prefixing the schema name in
the case of update statements, but does with searches ? Searching seems to
work without explicitely added prefix.
Cheers,
Marc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.scsys.co.uk/pipermail/dbix-class/attachments/20120223/7ed=
13636/attachment-0001.htm