Yo Thomas! > as you can see from the executed SQL: > "DELETE FROM vacancies WHERE v_id = ?" > the query is simply translated into a SQL delete statement not caring > about *any* auto-delete="true" settings!
Indeed - this had me 'flustered' :) > You have to use broker.delete(aVacancy) to remove the Vacancy instance > and all associated things! This fixed it - luckily we have 1 central place (which wraps OJB) so it was an easy fix :) ... > Maybe this should be made clearer in the docu... Yes :) Coz there is no distinction in the docs about delete or deleteByQuery (there reason we used deleteByQuery - is for mass deletes - it seemed a bit silly to first retrieve all of them just before finishing them off - ie only the 'linked' fields should be used, not so much the actual data) I figured that using deleteByQuery OJB would take care of that 'nasty' business :) Once again for clearing it up - our database got very big too quick :) Onno --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
