Re: Oracle Toplink



tricky wrote:
Somtimes when persisting object i [sic] get this error
ORA-00001: unique constraint (USER.INDEX_QUERY) violated

And this entry is not in database then but it doesn't seems to be a problem with duplicate key
Anybody help ?

Of course it "seems to be a problem with [a] duplicate" - that error message gives an overwhelming impression that that's the issue.

Are there fields besides the primary key with a UNIQUE constraint?

When you say "this entry" (presumably the object you wish to persist) "is not in [the] database", did you check to ensure that the object's values are distinct for every UNIQUE column in the table?

The "entry" will never be in the database - a *row* will be in a table and that row's *columns* will have values, some of which might conflict with the values you are trying to insert. The conflict doesn't have to be with the primary key, and it doesn't have to be for every column.

--
Lew
.



Relevant Pages

  • Oracle Toplink
    ... Somtimes when persisting object i get this error ... ORA-00001: unique constraint violated ... And this entry is not in database then but it doesn't seems to be a problem ...
    (comp.lang.java.programmer)
  • Re: WORD doc info into FMP?
    ... it appears that each line of the entry follows the format ... number of any given type of field (Location, script, sets etc.) you might ... into a separate record in a database, and a separate related "database 2" ... Ten Nights in a Barroom (New York State Archives) ...
    (comp.databases.filemaker)