Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • 3
    Better for what? What are you going to do with the URIs? Commented Mar 7, 2017 at 13:09
  • @AndresF. Read, store maybe do some analytics. Build back original URI and if it's web URL redirect. May do some searching that's why I think first is better. I am more interested in what advantage does one have over another or are there any problems in using one of them ? Commented Mar 7, 2017 at 13:31
  • 1
    @nikachx Is there any reason you can't just do both? Go with the first one, but add a column uri and store the unparsed version there. That way you can quickly search against that, or run analytics over the individual parts. Best of both worlds. The only argument against this is data redundancy, but I'd argue it's not all that redundant. Commented Mar 7, 2017 at 13:54
  • @neilsimp1 Good idea, post as answer. I want to get others opinion as well. Commented Mar 7, 2017 at 14:05
  • 1
    How are you going to use your data. Do you plan to query for information like "what is average query string length for port numbers given that protocol is https"? Commented Mar 7, 2017 at 14:30