Imho it depends. I don’t see any reason not to move it into a different structure if that suits you better
![](https://secure.gravatar.com/avatar/aec99942da9c84888960ccd6933a4ee7.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0026-72.png)
writen by Benedikt
I’m still too stuck on the relational model. episode_name must have a doc id or a path in Firebase. Can you put a string referencing it and fetch it when you need it? This will off course make you do extra queries, which is not cheap in firebase
![](https://avatars.slack-edge.com/2022-10-11/4228014909600_66ba9e0bc70b6194e36c_72.jpg)
writen by Bartolomeu Rodrigues
and i guess for that a relational database would suit me better no Bartolomeu Rodrigues?
![](https://avatars.slack-edge.com/2021-07-28/2322213143667_f9ad35c2dec28da258a5_72.jpg)
writen by Tiago Ferreira
I always do stuff with relational first, because most jobs and education hammered me that way. NoSQL for me is for Proof of concepts or data dumps
![](https://avatars.slack-edge.com/2022-10-11/4228014909600_66ba9e0bc70b6194e36c_72.jpg)
writen by Bartolomeu Rodrigues