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

Combine street.db and address.db into one database #255

Open
orangejulius opened this issue Apr 13, 2020 · 1 comment
Open

Combine street.db and address.db into one database #255

orangejulius opened this issue Apr 13, 2020 · 1 comment

Comments

@orangejulius
Copy link
Member

I think in the past we've discussed combining the two SQLite databases produced during an interpolation build. Would this still be a good idea?

It seems like it would be pretty nice since right now, we can't do joins between the names table that contains streetnames, and the address table that contains addresses. So something like SELECT * from address where names.name = "main street" has to be done manually through a query to each database.

My understanding is there are two database files to work around issues that SQLite has while writing to and reading from the same file. Have we learned more about SQLite since writing this code so that this isn't such a concern any more?

What would be the best way forward? Can we use a single database file throughout the interpolation build process? Or would it be better to add a finalization step that merges the two database files into one?

@missinglink
Copy link
Member

missinglink commented Apr 14, 2020

Joining between tables in different databases can be achieved using Attach Database.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants