Storing libs into BLOB

[Jean Marc Azerad]

Thanks Bas,

Problem solved, moved from DAM V2 ORACLE7 to DAM V2 ORACLE8 and it works....

But could not make DAM V3 work with Studio 4.2
To me they came with 4.2 but I can only make them work with 4.3 
Can someone remind me which was the first version with V3 dams ?

Thanks! 

J%


Le 10 déc. 2013 à 00:00, Bastiaan Olij <bastiaan at basenlily.me> a écrit :

> Hey JM,
> 
> Never done this with Oracle but we do this with Postgres. Only issue
> there is with escaping.
> 
> If you can't fix it a workaround that may solve you some headaches, even
> though it does increase store space ever so slightly, is to store your
> binary as base64 into a character field?
> Just use the good old UUencode and UUdecode functions.
> 
> cheers,
> 
> Bas
> 
> On 10/12/13 9:49 AM, Jean Marc Azerad wrote:
>> Hi all,
>> 
>> I have to store some libs in an Oracle Database.
>> Working with DAM V2, Studio 4.2
>> I get error messages when saving  (1459 or 1460) and errors when fetching... (kfetcherror)
>> When saving a text file, it works, when fetching, it always fails, even when the BOB field is empty.
>> 
>> My understanding is that it needs some kind of conversion that V2 DAM can't do and that I have to move to V3 DAM and do some settings with the $binarytoblog property.
>> 
>> It would save me a lot of time if someone could confirm or not that I cannot store a studio lib inside an Oracle BLOB with V2 Dams.
>> Not an issue, anyway, it's all written in the V3 mode, so it will not take much time to make the move, but I'd like to undersand and avoid going the wrong way just because I miss something.
>> 
>> Thanks!
>> 
>> JM_____________________________________________________________
>> Manage your list subscriptions at http://lists.omnis-dev.com
> 
> _____________________________________________________________
> Manage your list subscriptions at http://lists.omnis-dev.com