Timeline for Saving user searches to a database
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 8, 2017 at 15:51 | vote | accept | Soundwave | ||
| Jun 8, 2017 at 13:32 | comment | added | Soundwave | Please see my edited post: solution 3 and 4. | |
| Jun 8, 2017 at 13:29 | history | edited | Soundwave | CC BY-SA 3.0 | Added solution 3 and 4 |
| Jun 8, 2017 at 13:25 | comment | added | Soundwave | I would use a priceLow and priceHigh field. But I'm now more inclined to use the solution of Etsitpab Nioliv. What would be better, use solution 2 with date and time columns added compared to Etsitpab's solution? | |
| Jun 8, 2017 at 13:07 | comment | added | k3b | With solution 2 how would you handle ranges: i.e. price between 100 000 and 150 000? | |
| Jun 8, 2017 at 12:47 | answer | added | Etsitpab Nioliv | timeline score: 1 | |
| Jun 8, 2017 at 12:20 | history | edited | Soundwave | CC BY-SA 3.0 | New solutions |
| Jun 8, 2017 at 11:29 | answer | added | Antonio Parra | timeline score: 2 | |
| Jun 8, 2017 at 10:54 | answer | added | JacquesB | timeline score: 0 | |
| Jun 8, 2017 at 10:28 | history | asked | Soundwave | CC BY-SA 3.0 |