[TYPO3-dev] enforcement of uniqueness of fields

[Kasper Skårhøj]

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).

- kasper




On Apr 19, 2006, at 13:12 , Markus bertheau wrote:

> Hi,
>
> in versions 3.8.1 and 4.0 when a field is unique typo3 enforces that
> by appending a 0 so as to make the value unique (enter record one with
> "a" in unique field, secord record with "a" in unique field too,
> second record ends up with "a0"). This can cause quite some confusion.
> In particular I have a customer who saves note records in typo3, that
> have a note id field that looks like this:
>
> N67
> N102
> N120
>
> So when now someone accidentally enters N67 again, he will end up with
> N670, which is a perfectly valid note id, but is just the wrong note
> id for that note, and he is not notified of his mistake in any way. Is
> there a way to make typo3 output an error in such cases and give the
> user a chance to enter another note id?
>
> Thanks
>
> Markus Bertheau
> _______________________________________________
> TYPO3-dev mailing list
> TYPO3-dev at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev


- kasper

"A contribution a day keeps the fork away"
-------------------------------
kasper2006 at typo3.com | +45 20 999 115 | skype: kasperskaarhoej |  
gizmo: kasper_typo3