moved schema into an sql file for easier editing
added some torture testing

basically a way to add a gazillion patients, appointments, and
treatments

trying to see how the database would hold up ... was thinking I would
need an index on journal ts, but with 1448 entries in the journal it
seems to be working just fine ... but I should probably still have the
index, in particular as the number of appointments and journal entries
mounts, and it will grow more or less without bounds

in fact, I need to plan ahead. what to do when the database gets
ginormous? how big will it get? my test database was about 13k, and
the torture database with 413 patients, 1448 appointments and 5349
treatments is only 388k. but ...
updated timezone handling

now using timezone.localize instead of datetime.replace(tzinfo=) to
set the timezones, and it works much better to trust pytz to localize
timezones ... in particular, I had a bug with daylight savings time
that is now fixed
added an index to journal(ts) which should speed things up

I'm looking particularly at appointments, as the the number of
appointments grows without bound being able to efficiently locate a
range of appointments (to show what appointments fall on a day) will
be very valuable

but also I am always sorting a journal by 'ts DESC', so having the
index will make that operation more efficient as well