Andries Seutens wrote:
>
> Zend_Session_Namespace::setExpirationHops().
>
Oh, sweet! A much better solution than "I don't think that's possible". :)
Thanks for posting it.
- Lauren
--
View this message in context:
http://www.nabble.com/FlashMessenger-and-Controller-plugins---Help-wanted-tf4
You may have already solved this but I figured I'd post it in case it helps
anyone else. I've implemented your solution and experienced the same issue.
Andries Seutens wrote:
>
> The problem which I am now facing, is that the messages do not show up
> until the 2nd request.
>
Correct me if I'
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
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
