Interesting, PG3 takes the postgres jsonb type and converts it into a JsonObject for me.



So, instead of doing asDictionary, I suspect that I should I be able to work on the JsonObject directly without converting it.


heh...there was a moment of "oh! this changes everything" when I saw the

Object asPG3SqlLiteral

Where I thought I could store objects in the database Postgres database directly, but the attempt on an instance of the object only created the Object name

Since my objects are only data-buckets...I wonder if it is worth pursuing.


Has anybody done this?

I tried an experiment where I stored millions of objects in-image, which was fine except I needed 70Gb of RAM to store the image in-memory, and IIRC I only had about 35Gb of RAM.

If I could get that same sort of functionality by storing objects in Postgres, that would be awesome and a lot of fun to explore.


cordially 









---- On Thu, 07 Sep 2023 08:22:53 -0400 gettimothy <gettimothy@zoho.com> wrote ---

Perfect, thank you.

( (Json newWithConstructors: {JsonDummyTestObject.}) readFrom: '{"bar": "baz", "balance": 7.77, "active":false}' readStream) asDictionary


Now to figure out the reverse.


good fun.

thx






---- On Wed, 06 Sep 2023 13:34:51 -0400 Todd Blanchard via Squeak-dev <squeak-dev@lists.squeakfoundation.org> wrote ---




I recommend you use jsonb.

I would consider arrays and hstore to be legacy data types these days.

On Sep 6, 2023, at 5:54 AM, gettimothy via Squeak-dev <squeak-dev@lists.squeakfoundation.org> wrote:



I am leaning "Array types" but figure I should ask first.


cordially