[TYPO3-dev] enforcement of uniqueness of fields

[Markus bertheau]

Maybe a big red warning that the value was changed in order to ensure
uniqueness could be a first step to not letting happen data entry
errors as is the case now? I figure that would be easier to implement
than an ajax check and / or that the form is re-shown with all data.
What do you think?

Markus Bertheau

2006/4/19, Martin Kutschker <Martin.Kutschker at n0spam-blackbox.net>:
> Kasper Skårhøj schrieb:
> > In the old "classic backend" there was a check done which would  consult
> > the server before submitting the content. Today, the problem  is that
> > the uniqueness check is done after the content is submitted.  It is
> > therefore found acceptable to silently create a unique value  incase it
> > isn't unique when submitted. This is to avoid having to  implement that
> > the form is re-shown with all data which is especially  difficult with
> > uploaded files.
> >
> > My suggestion is that with todays AJAX technology someone writes an
> > addition to TCeforms which allows to check unique fields as a part of
> > the java script evaluation which also happens on any other field  (like
> > dates, integers etc).
>
> Whatever. I've run also into multiple times into the problem that TYPO3
> silently changes the page alias.
>
> But a check prior to form submission may fail as TYPO3 does no table
> locking. So an AJAX check is nice, but a race condition may occur. But of
> course better a check that works 99% rather than none. So AJAX gurus,
> please step forward ;-)
>
> Masi
> _______________________________________________
> TYPO3-dev mailing list
> TYPO3-dev at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev
>