<p>I can understand why we don't want to ignore / throw away any of the <code>addr:*</code> information; After all, there probably was a reason why it was entered in the first place. However, can't we have both, efficient storage for the common case and no lost information? You could use columns for the "usual" address information which is already explicitly interpreted, like <code>addr:housenumber</code>, <code>addr:street</code>, <code>addr:place</code>, <code>isin</code> and store all other, currently uninterpreted <code>addr:*</code> fields in the new HSTORE column, making it NULL in the common case?</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/openstreetmap/osm2pgsql/pull/737#issuecomment-294902706">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AD2-7pgAJN0lfhKMoRmk5MOCw1IGqCGwks5rxOX1gaJpZM4M3wS8">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/AD2-7vfMVw_wdF0Gt_crPBhUNf3Guz26ks5rxOX1gaJpZM4M3wS8.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/openstreetmap/osm2pgsql/pull/737#issuecomment-294902706"></link>
  <meta itemprop="name" content="View Pull Request"></meta>
</div>
<meta itemprop="description" content="View this Pull Request on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/openstreetmap/osm2pgsql","title":"openstreetmap/osm2pgsql","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/openstreetmap/osm2pgsql"}},"updates":{"snippets":[{"icon":"PERSON","message":"@roques in #737: I can understand why we don't want to ignore / throw away any of the `addr:*` information; After all, there probably was a reason why it was entered in the first place. However, can't we have both, efficient storage for the common case and no lost information? You could use columns for the \"usual\" address information which is already explicitly interpreted, like `addr:housenumber`, `addr:street`, `addr:place`, `isin` and store all other, currently uninterpreted `addr:*` fields in the new HSTORE column, making it NULL in the common case?"}],"action":{"name":"View Pull Request","url":"https://github.com/openstreetmap/osm2pgsql/pull/737#issuecomment-294902706"}}}</script>