Timeline for Write complex query OR write simpler queries and combine the results in Backend service?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 12, 2020 at 5:57 | vote | accept | Jahirul Islam | ||
| Jan 16, 2020 at 7:06 | comment | added | Jahirul Islam | Currently, there is no real plan to target a different DB. I just need to make sure the SQLs don't get overcomplicated and remain maintainable without too much effort. | |
| Jan 16, 2020 at 6:47 | comment | added | Christophe | @JahirulIslam Yes, this is a very valid argument if you target a cross db platform, or if you target a document oriented like db like Mongodb, where the joins require more gymnastics. But is it a real intention or just a possible future? And what about delivering the features fast and refactor later if needed? (which is in fact the idea behind my “combination” suggestions) | |
| Jan 16, 2020 at 5:51 | comment | added | Jahirul Islam | All very good points. So I guess the answer would be "it depends". The reason I wanted more DB independence is that the DB structure is a WIP and may very well go through some changes before being finalized. So, writing complex queries would mean that these queries need to be modified if some changes occur. And if that happens modifying complex queries would be a lot harder task than modifying simple queries and increase the possibility of making a mistake. | |
| Jan 15, 2020 at 22:25 | history | answered | Christophe | CC BY-SA 4.0 |