Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve creation of osm.pgosm_flex to use LuaSQL #183

Closed
rustprooflabs opened this issue Oct 23, 2021 · 0 comments
Closed

Improve creation of osm.pgosm_flex to use LuaSQL #183

rustprooflabs opened this issue Oct 23, 2021 · 0 comments
Labels
Technical Debt Not broken, not new, but not right either!
Milestone

Comments

@rustprooflabs
Copy link
Owner

Details

Created as follow up to #182, this deserves dedicated issue for tracking instead of working into that PR.

What to do

Update osm.pgosm_flex table creation/population to use LuaSQL instead of the current hack in osm2pgsql process. It is pretending to be a single-row layer in its current state and is the cause of this WARNING during processing.

WARNING: Table 'pgosm_flex' doesn't have an id column. Two-stage processing, updates and expire will not work!

Resolving this should remove the only known block to testing using osm2pgsql with --append, see disucssion: #167

@rustprooflabs rustprooflabs added the Technical Debt Not broken, not new, but not right either! label Oct 23, 2021
@rustprooflabs rustprooflabs added this to the 0.4.0 milestone Oct 23, 2021
rustprooflabs added a commit that referenced this issue Oct 26, 2021
…olumns, each import to an existing database will add a row. #183
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Technical Debt Not broken, not new, but not right either!
Projects
None yet
Development

No branches or pull requests

1 participant