Object Storage

[iamjoshljohnson]

Noticed that Flintstone doesn't currently support object storage per key but will support an object loaded into an array.

Should there be support for object storage directly?

[TheDigitalOrchard]

You could serialize the objects and store that as a string value.

[iamjoshljohnson]

Flintstone will already do that for you. If you store an array with one object in it, FlintstoneDB will serialize the object when it stores. But then I am storing an array with an object.

I think Flintstone can support storing Objects directly relatively easy. Wanted to see if you guys agreed. That way a User key could be associated with a User object.

[iamjoshljohnson]

It looks to me that Flintstone already supports storing objects directly. I will fork update the datatype check to remove the this restriction.

[iamjoshljohnson]

Im going to look into this again and see if I can get it working. I think this would be a great addition to this piece of software!

[fire015]

Interesting piece of code from Laravel... https://github.com/laravel/framework/blob/5.0/src/Illuminate/Queue/SerializesModels.php

[iamjoshljohnson]

Hmmm...That looks interesting! I'll take a look at this

[iamjoshljohnson]

So the problem is with an associative array! We can't store an associative array in Json. It is physically impossible. So I think instead of just allowing the data to be stored, there should be a constraint to now allow you to store associative arrays in a JSON format. This makes sense to me. Any thoughts?