On Monday 30 June 2003 2:45 pm, Jason Sibre wrote:
> > -----Original Message-----
> > From: quixote-users-bounces@mems-exchange.org
> > [mailto:quixote-users-bounces@mems-exchange.org]On Behalf Of Mark
> > Bucciarelli
> > Sent: Monday, June 30, 2003 1:19 PM
> > To: quixote-users@mems-exchange.org
> > Subject: Re: [Quixote-users] Draft of Quixote white paper
> >
> > 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.
>
> That's a good point, and one that I hadn't considered.  Your idea
> would work well, but I don't like the fact that in a high traffic
> site, the same timestamp could point to two different appointments
> that were created at the same time.

I think you misunderstood me.  I meant to use a compound key that
uniquely identifies each appointment (name + start_time +date).

[snip pseudo_GUID idea]

> I kinda dislike that approach however.  It
> makes for long, ugly, hard-to-type id numbers.

I agree.

[snip form_token idea]
[snip storing auto_id and guid idea]

> I've used the guid approach in a production app before (ASP - SQL
> Server) and it worked...  But it really felt like a hack.

I think I'll store a (last_form_token, recno) tuple in the user's
session.  When they save, I can check if the form_token ==
last_form_token.  If it does, I update that recno, otherwise it's a
new record.  Then update the tuple.

Mark