Timeline for Minimize touching the already-working code when a radical change is required
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 25, 2014 at 7:51 | history | edited | Barry Staes | CC BY-SA 3.0 |
fixed typo, improved example code comments.
|
| Feb 25, 2014 at 5:21 | vote | accept | Mahdi | ||
| Feb 24, 2014 at 10:47 | review | First posts | |||
| Feb 24, 2014 at 11:21 | |||||
| Feb 24, 2014 at 10:46 | comment | added | Mahdi | Thanks for the advices, they are really useful. The design is not very well-thought, also it's suffering from other radical changes during the time, that's basically how we get here. The SQL queries are so costly here -- normalized db requiring multiple joins, that's why we have everything in an array, just to save database queries, but I totally agree with your idea about the structure. Thanks again for the answer. | |
| Feb 24, 2014 at 10:30 | history | answered | Barry Staes | CC BY-SA 3.0 |