Skip to content

use BigInt instead of Int for large geonames, optimize SQL import - #65

Open
merkalev wants to merge 2 commits into
openplaceteam:mainfrom
benchware:main
Open

use BigInt instead of Int for large geonames, optimize SQL import#65
merkalev wants to merge 2 commits into
openplaceteam:mainfrom
benchware:main

Conversation

@merkalev

@merkalev merkalev commented May 29, 2026

Copy link
Copy Markdown
Contributor

changes

  • Use BigInt instead of Int for large geonames like allCountries.txt, etc.....
  • Optimize SQL import to make it much faster by using createMany batching instead
  • Fix Error 1020 race condition

The reason I made this pull request was I accidentally used allcountries.txt, but hopefully this may fix some future issues

@merkalev

Copy link
Copy Markdown
Contributor Author

actually i shouldn't replace kd-tree

@merkalev merkalev changed the title use BigInt instead of Int for large geonames, optimize SQL import and replace KD-Tree use BigInt instead of Int for large geonames, optimize SQL import May 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant