Add option to don't store #type along json data
B-Galati opened this issue · 17 comments
Hello!
What about adding Deserialization type in the app codebase instead of storing it in the database?
Something like:
/**
* @ORM\Column(type="json_document", class="App\Address", options={"jsonb": true})
*/
public $foo;class could also be in options if it's easier to manage.
It's a bit like doctrine @Embedded.
My concern is that having classname stored in DB is hard to maintain as a migration strategy has to be established on each namespace change.
You mean for inner documents? We could even use PropertyInfo to get the type instead of adding a new option.
But there is a limitation with this approach: currently JSON ODM allows to store very variable data (mixed). With this approach, it's not possible anymore.
What would be possible to avoid having to store FQCN along json data in your opinion?
I like the idea, however, it won't work with nested entities of different types.
What might work is some kind of mapper. So instead of #type you store #mapKey (or whatever) and in the annotation you can specify something along the lines of
typeMapping={"foobar": "App\Foobar", "otherkey": "App\Other"}
It would be also compatible with the existing solution so it's totally opt-in.
You are likely already aware, but a fork of this library says it has moved the metadata out of the field: https://github.com/goodwix/doctrine-json-odm
Unfortunately the commits are not well-organised, so there is not a specific commit where they implemented this.
What do you think about by typeMapping solution? If that would solve your problem (and there are a few thumb ups so probably it would for others), why not make a PR? 😄
@Toflar It looks like a good solution to me 👍
Regarding the PR, I won't be able to do it honestly.
FYI, we choose another solution: custom doctrine type for each object. It is based on this article https://matthiasnoback.nl/2018/03/ormless-a-memento-like-pattern-for-object-persistence/.
It's a lot less generic but it's doing the job pretty well for us as we don't need a lot of custom type.
You are likely already aware, but a fork of this library says it has moved the metadata out of the field: https://github.com/goodwix/doctrine-json-odm
Indeed, but like @dunglas said, with this approach you can't store variable data, @Toflar idea seem more flexible IMO.
I think it would be great to have the possibility to not store the #type along with the great type map done in PR #118.
It makes sense when the stored data are always of the same type: in this case you don't want to store this useless metadata, you only want to (de)serialize your data with the same class.
@alanpoulain I might misunderstand your use case, but wouldn't a custom doctrine type would suit better if it's always the same class?
Sure but you need to write custom code to (de)serialize your data. Having it done by this library out of the box would be nice (that's what https://github.com/goodwix/doctrine-json-odm does).
@alanpoulain I might misunderstand your use case, but wouldn't a custom doctrine type would suit better if it's always the same class?
It's much quicker to annotate a few times on a POPO that you probably already created, than create a custom Doctrine Type, and then possibly map it, etc. Also, not everyone is familiar with being able to create a Doctrine type, and have to worry about (de)serializing it properly, etc. I'm guessing quite a few of them would come to this repo to get a quick 'composer require <>' and expect to work with POPO's.
PR welcome then!
PR welcome then!
Wouldn't it be quicker and easier for you to do it as you know the codebase already and are already in the mindset? :) Not like I haven't done it before, but I'd have to fork the project, analyze it, coordinate, find out your coding style, etc. I'm not entirely opposed to doing it if I really want it, but is there any reason you can't?
but is there any reason you can't
Time and other priorities 😅