This direct action is running on an application that has around 20instances running. So some how one of the other instances is insertinga new keyword and the other instances continue to report it as notbeing there.You could have a race condition where two instances check the database for the same k
Thanks Chuck and Robert.
I'm currently catching, reverting and otherwise ignoring the exception
being thrown. I just didn't know if there was anything else I should
have been doing. I appreciate your time and help on this issue.
- Eric
On 12/2/05, Chuck Hill <[EMAIL PROTECTED]> wrote:
> Eric,
>
Eric,
As far as I know there is only one certain way to do this:
1. Add a unique constraint on descriptor in NewKeyword in the DB if
you don't have one already
2. Keep the existing checks in place as they will catch much of the
attempts at duplication
3. When a NewKeyword is saved, wrap the
Chuck,
You are right on all accounts.
Here's a little broader understanding of the system. It's a content
finder, storage and retrieval system based on keywords. A client (a
client in general terms not Java client, be it browser or other
script) queries the system using a URL with the keyword in
Hi Eric,
I am not sure that I am following this correctly, so some questions
below.
On Dec 2, 2005, at 8:26 AM, Eric Stewart wrote:
Hello everyone,
I'm having a problem where it appears I'm getting stale data from the
editing context.
I have a direct action that is inserting keywords int
Hello everyone,
I'm having a problem where it appears I'm getting stale data from the
editing context.
I have a direct action that is inserting keywords into a database
table. The word itself (called "descriptor") is unique because I don't
want the same keyword in the system twice.
When a direct
