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?
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
namestable that contains streetnames, and theaddresstable that contains addresses. So something likeSELECT * 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?