Comment 1 for bug 1694504

Thanks for this Tyson.

Currently to manage this - I would suggest not loading the queXS_US.sql file which contains the US prefixes, unless you are located in the US. It would be great if you could contribute an equivalent Canadian list.

If you are calling across multiple countries, then the system would need to updated to accommodate this.

One user tried this:

- empty the sample_prefix_timezone table
- empty the sample_state_timezone table
- empty the sample_postcode_timezone table

- load custom values in the sample_state_timezone table, that will be known in your sample, eg:

val,Time_zone_name
---,--------------
VIC,Australia/Victoria
NSW,Australia/NSW
WA,Australia/Perth

- Make sure your sample file contains a column with a matching "val" record

- When importing the sample, assign that column as type: "State"

The matching timezone will then apply to the record.

Adam