Re: At the end of my teather with LSMB

[Luke <..hidden..>]

On Wed, 28 May 2008, Chris Travers wrote:

> However, this doesn't get to the question as to what qualifies an
> invoice number as unique, considering the following possibilities:
> 
> "12345"
> "12345."
> "12345 "
> "12345,"
> "12345-"
> "12345V"
> "12345[tab]"
> "12345-VOID"
> " 12345"
> " 12345 "
> " 1 2 3 4 5 "
> 
> All of the above woud be alowed using a unique index or constraint.

I discussed all of that in detail in another message.  I can repost that 
section, if it's worth seeing again.

> I am wondering if stuff beyond a simple unique constraint on
> ar.invnumber should be pushed to the regulatory compliance modules for
> specific regions..

That would be good for some things, but whitespace at the ends of the 
string should be safe to eliminate everywhere, and spaces within as well, 
but with a checkbox in defaults.
Allowable characters configurable in defaults, with a starting (default) 
effective value of the regexp "[a-zA-Z0-9-]" (expressed in a 
non-programmer friendly way, of course, maybe with selectable options).

Regards,

Luke