You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using doctrine phpcr odm for my application with the doctrine dbal transport. Because of the need to store large files in the phpcr (>200mb) I wanted to switch to midgard2. The problem now is, that the content of nt:file won't get stored any longer. After creating the nt:file document the content is definetly in the object, but after persisting its gone. Properties like size and mime type get properly persist. The row in the blobs table is there and the file gets created but the content of the file is everytime "ÿØÿà" if the file is a image. if the file is a pdf its "%PDF-1.4
%âãÏÓ
4 0 obj
<</Type/XObject
/Subtype/Image
/Width 3508
/Height 2480
/BitsPerComponent 8
/ColorSpace/DeviceRGB
/Filter /DCTDecode
/Length 267934
stream
ÿØÿà"
seems like the stream only persists some header information.
I know this sounds like a doctrine issue, but the implementation worked so far with another transport.
best regards
The text was updated successfully, but these errors were encountered:
I'm using doctrine phpcr odm for my application with the doctrine dbal transport. Because of the need to store large files in the phpcr (>200mb) I wanted to switch to midgard2. The problem now is, that the content of nt:file won't get stored any longer. After creating the nt:file document the content is definetly in the object, but after persisting its gone. Properties like size and mime type get properly persist. The row in the blobs table is there and the file gets created but the content of the file is everytime "ÿØÿà" if the file is a image. if the file is a pdf its "%PDF-1.4
%âãÏÓ
4 0 obj
<</Type/XObject
/Subtype/Image
/Width 3508
/Height 2480
/BitsPerComponent 8
/ColorSpace/DeviceRGB
/Filter /DCTDecode
/Length 267934
seems like the stream only persists some header information.
I know this sounds like a doctrine issue, but the implementation worked so far with another transport.
best regards
The text was updated successfully, but these errors were encountered: