[Roadster] Converting TIGER data to a MySQL database

[Barry Gould]

ISTM that there could be a POI table per user, but in the same 
database and datastore as the other tables.
Of course, this would require someone with MySQL Create permissions 
to setup a new user

Or, maybe just one POI table, and a 'favorites' table per user, or 
one favorites table with a 'user' column (then this wouldn't require 
any system privileges to add a new user, but a malicious user could 
potentially read and/or delete other users favorites. I'm not sure 
this is a real concern though... roadster isn't typically going to be 
run on a multi-user server, just on private of family laptops, etc.).

Barry

At 02:37 PM 2/13/2006, Jeff Garrett wrote:
>I'm still a little bit worried though.  In the proposed
>packaging thing above, it'd mean we would need at least two MySQL
>embedded servers (one for the system db and one for the per-user) if I
>understand things and maybe more (if you have data for multiple
>states...).

>In the scheme I suggested, we essentially want to process the TIGER data
>and split it into different parts (by state or whatever).  The advantage
>of having an SQL-like interface is that we can index the data, but my
>scheme would be unreasonable if that interface has a large overhead...
>I'm thinking SQLite would be better.  What do you think?