oatpp-postgresql icon indicating copy to clipboard operation
oatpp-postgresql copied to clipboard

Large Object Support?

Open acidtonic opened this issue 4 years ago • 5 comments

Curious if there are any plans for large object support? Normally I'd just store in the filesystem with a checksum in the DB but I have a need for the streaming/seeking abilities that come with the large object api. I don't even need all that fancy support here only basic crud and from my other tools I can do the rest.

I see TEXT support but that's 1GB limited and I'm doing neural network stuff that easily eclipses that with larger models so I truly need large object support or perhaps another document db to go alongside.

Wanted to ask in case the docs were out of date. I also lurk in the Gitter chat and can ask there if collaboration is needed. Thanks!

acidtonic avatar Feb 04 '21 04:02 acidtonic

Hello @acidtonic ,

I'm currently working on finishing arrays functionality. Large objects can be added afterward. But most probably it'll happen (large objs) in the next release 1.3.0.

Regards, Leonid

lganzzzo avatar Feb 04 '21 08:02 lganzzzo

I seen arrays and 1.2.5 get released, just wanted to see how large object support is going.

Also if I use TEXT do I need to do my own base64 encoding?

acidtonic avatar Apr 05 '21 15:04 acidtonic

@acidtonic ,

Yes, arrays were added in 1.2.5.

Also if I use TEXT do I need to do my own base64 encoding?

Yes, if your binary data can contain a '\0' char - then base64 encoding may be a good solution for you.

lganzzzo avatar Apr 05 '21 17:04 lganzzzo

just wanted to see how large object support is going.

Yes, I plan to add it in 1.3.0

lganzzzo avatar Apr 05 '21 17:04 lganzzzo

Hi @lganzzzo Large Object Support is integrated in 1.3.0 or it is work still in progress ? I couldn't find any example on how to use this in oatpp framework.

Jithu-08 avatar Aug 18 '23 10:08 Jithu-08