What is the expected behavior of Hibernate in case of a double delete of an entity ?

I have some unit tests for detecting the raising of a StaleStateException in that situation:

// delete the user
userService.delete(user);

try {
// try to delete it twice
userService.delete(user);
fail("Deleting twice should raise an StaleStateException");
}
catch(StaleStateException e) {
// expected
}


The tests pass with MySQl and fail with Oracle 9i.
Shouldn't hibernate provides a consistant behavior whatever the underlying database ??

TIA.


Hibernate version:
3.1rc3

Mapping documents:
N/A

Code between sessionFactory.openSession() and session.close():
session.delete(id);
or
session.delete(entity);

Full stack trace of any exception that occurs:
N/A

Name and version of the database you are using:
MySQL 4.xx
Oracle 9i

The generated SQL (show_sql=true):

Debug level Hibernate log excerpt:

double delete isn't error - you will do nothing second time, only

try from sql tool (sqlplus or mysql, psql tool )

delete from table
where id='nonexists'

you get only 0 rows deleted or like message and no error

At the SQL level (using sqlplus or whatever) you are certainly right.

But at the Hibernate API level this is not always the case;
As I said before, the following code:


will pass without any error when the underlying database is Oracle9i but it will throw a StaleStateException with MySQL.

In this precise case, Hibernate exibit different behaviors depending on the underlying database. Isn't it a code smell ? I am just asking.

it is problem with mysql, probably
postgresql don't return error for deleteing with no row - you can have return value that number of rows is 0

delete command can delete 0 or more rows and if command is correct then no error for any number of rows

try mysql from command (mysql client) - i haven't mysql and can't try