Timeline for How to efficiently store locations?
Current License: CC BY-SA 3.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 10, 2017 at 10:52 | vote | accept | vardius | ||
| Nov 10, 2017 at 9:06 | answer | added | Bernhard Hiller | timeline score: 4 | |
| Nov 9, 2017 at 4:41 | answer | added | jpotts18 | timeline score: 6 | |
| Nov 8, 2017 at 5:04 | comment | added | vardius | So you do not see any other better solution ? Or more things that i should consider when designing location based service ? | |
| Nov 8, 2017 at 5:03 | comment | added | Euphoric | @MichaelGreen Not only addresses. But any kind of geographic data. Especially if you want to build relationships between them. | |
| S Nov 8, 2017 at 4:59 | history | suggested | Michael Green | CC BY-SA 3.0 |
More typos
|
| Nov 8, 2017 at 1:51 | review | Suggested edits | |||
| S Nov 8, 2017 at 4:59 | |||||
| Nov 8, 2017 at 1:49 | comment | added | Michael Green | There are many overlapping questions on DBA.SE. In short: addresses are hard; they vary a lot between regions. Aus Post is quite consistent, however. Your plan will likely work well enough here. | |
| Nov 8, 2017 at 1:48 | comment | added | vardius | @CandiedOrange I've added use case example | |
| Nov 8, 2017 at 1:47 | history | edited | vardius | CC BY-SA 3.0 |
added 250 characters in body
|
| S Nov 8, 2017 at 1:45 | history | suggested | Michael Green | CC BY-SA 3.0 |
formatting, typos
|
| Nov 8, 2017 at 1:45 | review | Suggested edits | |||
| S Nov 8, 2017 at 1:45 | |||||
| Nov 8, 2017 at 1:16 | comment | added | candied_orange | They all look like strings to me. Why are you trying to store them as something else? What is that getting you? | |
| Nov 8, 2017 at 1:12 | history | edited | candied_orange | CC BY-SA 3.0 |
edited title
|
| Nov 8, 2017 at 0:58 | history | edited | vardius | CC BY-SA 3.0 |
added 122 characters in body
|
| Nov 8, 2017 at 0:53 | history | asked | vardius | CC BY-SA 3.0 |