I'm not very familiar with Oracle either but it seems like CLOB is for Oracle what TEXT is for Postgres and MySQL.

There is a function in the dbmail-code called 'db_result_get_blob', it is used for several things,

like '_fetch_headers'. HEADERVALUE is a CLOB.on Oracle and TEXT on Postgres.

Perhaps this function should have been used on '_fetch_envelope' too?

It will probably be easiest for me to just use getBlob instead, as for upstream, perhaps it's a good idea to use

'db_result_get_blob' for all TEXT/CLOB-fields if it works?

Thank you very much for the help!

Regards,

Mats Christensen

On Fri, Jan 31, 2014 at 11:34 AM, Paul J Stevens <paul@nfg.nl> wrote:

Mats,

Looking at the dbmail code involved I notice that the Oracle schema is
the only one that defines the 'envelope' field as a CLOB. PostgreSQL and
MySQL both treat it as a TEXT field. So DBMail uses ResultSet_getString
to retrieve the value, not ResultSet_getBlob.

That might well explain the NULL result.

Now *why* Oracle defines that field as a CLOB, I don't know. I'm not
familiar with Oracle's data-types, but if you can please use a TEXT
field instead.

A cursory check of the oracle schema reveals one other instance where
CLOB is used, but TEXT seems more appropriate, i.e. in the
sievescripts.script field.

--
________________________________________________________________
Paul J Stevens pjstevns @ gmail, twitter, github, linkedin

* Premium Hosting Services and Web Application Consultancy *

www.nfg.nl/info@nfg.nl/+31.85.877.99.97
________________________________________________________________
--
To unsubscribe:
http://www.tildeslash.com/mailman/listinfo/libzdb-general