[Gnumed-devel] rschedule

[Syan Tan]

select * FROM rschedule;
+-------------+------------+------------+-----------+-------------------+-----------------------------------+---------------------------------------------------------+-----------------+
| provider_no | sdate      | edate      | available | day_of_week       | avail_hourB                       | avail_hour                                              | creator         |
+-------------+------------+------------+-----------+-------------------+-----------------------------------+---------------------------------------------------------+-----------------+
| 999998      | 2006-06-01 | 2006-07-30 | A         | 2 3 4 5 6 |2 3 6  | <MON></MON><TUE></TUE><FRI></FRI> | <MON></MON><TUE></TUE><WED></WED><THU></THU><FRI></FRI> | oscardoc,doctor |
| 999998      | 2006-06-30 | 2006-07-30 | A         | 2 3 4 5 6 |2 3 6  | <MON></MON><TUE></TUE><FRI></FRI> | <MON></MON><TUE></TUE><WED></WED><THU></THU><FRI></FRI> | oscardoc,doctor |
+-------------+------------+------------+-----------+-------------------+-----------------------------------+---------------------------------------------------------+-----------------+
2 rows in set (0.00 sec)

for some reason,  there seems to be an empty list in the rschedule setting jsp page, next to the days of week selection

list , which I presume is for setting the hours of the day, as there is also a << button next to each day of week,

so I can't set the hours working for the day of the week.

As you can see, the table is very non third form normalized, (it's probably not even in 1st form),

with the day_of_week being a space separated string of digits , and a | used to separate weeks, if an alternate

week schedule is chosen. It would be nice if the format they used was something like the ical format, which

is the internet calendar format, as it might mean import and export from other programs is easier.

Also , the available hours format looks like it could be xml, so in between the <MON></MON> there might

be something like <SESSION><START>9:00</START><END>13:00</END></SESSION>  or something

like that. Again , you could see it from a purist angle, and ask why not store it as linked tables schedule, sched_week,

sched_day, sched_session,  or something like that.

But again, hey , it works, so if it ain't broke ...