On Friday 27 June 2003 9:24 pm, Jason Sibre wrote:

> I recently addressed the issue you describe by using the underscore
> (_) as a url placeholder indicating a new object.

hmmm, i think this breaks the back button.

open ./jun-6/_/edit
fill out form
click save (new record id = 6)
oops, make a mistake, now click back.

quixote goes to ./jun-6/_/edit not ./jun-6/6/edit

i don't think you can rely on a browser refresh when someone clicks
the back button.

i could use the start time as the url component i.e.,
./jun-6/11:00a/edit, but this would disallow more than one
appointment at the same time.  And if they changed the appointment
start time after clicking the back button, it's the same problem.

i think the best solution is to check for existing appointments when
they save a new one.  if there is another appointment with the same
date, start time and title, assume it's the same appointment, and
overwrite instead of inserting (being sure to delete the old one).
yuck.

i wonder if all this machinery could be abstracted into a base class.

cheers,

mark