<p></p>
<blockquote>
<p dir="auto">The properties table does change the game a little bit: you cannot do two imports with different prefixes on the same database anymore without breaking something. That was not the case before. The recommended work-around is to use schemas but, again, we do have some historic baggage here.</p>
</blockquote>
<p dir="auto">I guess I'm not aware of the baggage with schemas.  How does this interact with flex styles that save tables to schemas? A good portion of what I've found useful lately is loading a variety of<br>
<a href="https://blog.rustprooflabs.com/2023/08/load-right-amount-of-openstreetmap" rel="nofollow">different data, with different styles, to different schemas</a>. The styles I use <a href="https://github.com/rustprooflabs/pgosm-flex/blob/main/flex-config/style/building.lua#L14">set schema dynamically</a>.</p>
<p dir="auto">There are already limitations around multiple sources within one DB with replication (e.g. <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1434811910" data-permission-text="Title is private" data-url="https://github.com/osmcode/pyosmium/issues/214" data-hovercard-type="issue" data-hovercard-url="/osmcode/pyosmium/issues/214/hovercard" href="https://github.com/osmcode/pyosmium/issues/214">osmcode/pyosmium#214</a>), I'd prefer not to see multiple sources further limited.  If I have to drop the properties tables to load into multiple schemas I can, but that seems to dilute the purpose of that table in this scenario.</p>
<p dir="auto">Would it be possible to define which schema the properties table is saved in?  This seems like it would still allow supporting multiple imports to a single database w/out losing the addition of safety against accidentally doing bad things. Another possible approach could be changing the table from a tall table (2 columns, many rows) into wide structure. Either via dedicated columns or a JSON/JSONB column?  This would allow adding a <code class="notranslate">schema_name</code> column to allow support of that.</p>
<blockquote>
<p dir="auto">I'd rather do it without introducing an additional command line.</p>
</blockquote>
<p dir="auto">Understandable, I'm okay with your suggestion to manually delete the table when needed.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />Reply to this email directly, <a href="https://github.com/osm2pgsql-dev/osm2pgsql/pull/2085#issuecomment-1846425084">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AA6353S6S7S45KW4HYUXNCDYIJVYHAVCNFSM6AAAAAA5EZ66OCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBWGQZDKMBYGQ">unsubscribe</a>.<br />You are receiving this because you are subscribed to this thread.<img src="https://github.com/notifications/beacon/AA6353QXNXYRZSRLOCJ5UYLYIJVYHA5CNFSM6AAAAAA5EZ66OCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTOBY27Y.gif" height="1" width="1" alt="" /><span style="color: transparent; font-size: 0; display: none; visibility: hidden; overflow: hidden; opacity: 0; width: 0; height: 0; max-width: 0; max-height: 0; mso-hide: all">Message ID: <span><osm2pgsql-dev/osm2pgsql/pull/2085/c1846425084</span><span>@</span><span>github</span><span>.</span><span>com></span></span></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/osm2pgsql-dev/osm2pgsql/pull/2085#issuecomment-1846425084",
"url": "https://github.com/osm2pgsql-dev/osm2pgsql/pull/2085#issuecomment-1846425084",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>