Map array structure in php
I need to find a nice solution to map one database model to another, third party model.
The code currently has to do something like:
'HomePhone' => $customer['details']['phone']['home']
As you can imagine, if
$customer['details']['phone']['home'] is used multiple times, it becomes a nightmare to modify the keys if the database changes (as it does).
So I would like to have a config to use for the mapping, for example
$map = [ 'HomePhone' => 'customer.details.phone.home' ]
Such that, I can simple use
$map['HomePhone'] throughout, and only need to change the one spot for the data model, eg to change it to
If this is the structure of the config item, how would I take
customer.details.phone.home and explode it to
[customer][details][phone][home] within the assignment above ?
Is this thinking valid, or is there a better way ? Thanks
welcome to data abstraction
Generally speaking, if you have some datum and you want to get a specifc piece of data out, you write a selector. The good news is, you're on the right path – only you're just trying to solve it a little incorrectly …
Now whenever you need to access this property in your code, you will always do so using
The benefits of this are absolutely tremendous.
The person trying to get data from
$customerdoesn't need to know anything about how it's structured.
What if the data were to become extremely complex, with hundreds of fields and dozens of levels of nesting? It might be really frustrating to have to look at a reference object to re-learn how to access a field you need to read.
I can always remember
customerHomePhone($customer)but it's much harder to remember …
detailsplural? Wait, yeah, I think
phoneswas pluralized but
detailwas singular... dammit !"
What it also means is that you have freedom to change where the home phone data (or any data) is stored – change it however you want – and all you have to do is update it one place in your app.
Say you change it to be stored as …
… all you have to do is update
$customermight even change more significantly. Maybe you'll use
stdClassinstead of array so the selector becomes …
It doesn't matter. As long as the selector points to the correct value in whatever data structure you're using, the rest of your app is shielded from the change and continues to work perfectly.
Of course it would make sense to build other selectors as well …
Would you like to learn more about data abstraction? Check out these links:
Maybe you don't like the functional approach, or maybe OOP gels better with your existing app.
classes are OOP's golden hammer when it comes to data abstraction – or any abstraction for that matter.
This might seem like a lot of work, but that's only because your
$customerdata is so complicated. If your customer data was flat, you'd still want to use data abstraction, but you could do so in a much more simple way …