, September 28, 2007 11:50 PM
> To: lauren49
> Cc: fw-general@lists.zend.com
> Subject: Re: [fw-general] Validation for multi-column unique
> constraints
>
> I prefer combination of the following methods:
> 1. Check the uniqueness using a SELECT query.
> 2. Display error
>
On 9/30/07, lauren49 <[EMAIL PROTECTED]> wrote:
>
>
> Alex Netkachov wrote:
> >
> > I prefer combination of the following methods:
> > 1. Check the uniqueness using a SELECT query.
> > 2. Display error
> > 3. After fixing error, execute data modification statemenet.
> > 4. In case of error I can do
Alex Netkachov wrote:
>
> I prefer combination of the following methods:
> 1. Check the uniqueness using a SELECT query.
> 2. Display error
> 3. After fixing error, execute data modification statemenet.
> 4. In case of error I can do either of the following:
> 4.1. parse error message and displa
I prefer combination of the following methods:
1. Check the uniqueness using a SELECT query.
2. Display error
3. After fixing error, execute data modification statemenet.
4. In case of error I can do either of the following:
4.1. parse error message and display error or if it fails
4.2. just show t
Hi,
I understand that checking for a value's uniqueness against a db table
within in application is not a stable method and should not be relied upon
but the exception message thrown by a save attempt when a value is not
unique really doesn't make much sense to the user
Caught exception: Zend_Db
