Right now, mapPacker is set to write data to a database table that is assumed to already exist with a particular column schema.
Since mapPacker will be the first service to touch this database table for a new instance, we can reason that it's also the best tool to instantiate the table. So, let's have mapPacker create the offline_maps database table if it doesn't already exist.
Right now, mapPacker is set to write data to a database table that is assumed to already exist with a particular column schema.
Since mapPacker will be the first service to touch this database table for a new instance, we can reason that it's also the best tool to instantiate the table. So, let's have mapPacker create the
offline_maps
database table if it doesn't already exist.