From: youjun g. <you...@ya...> - 2010-03-25 23:29:16
|
Bill traversed all TB tables and finally found out to delete a matrix record, we will need to cascade delete related data from more than 50 other tables. Surprisingly the bottle neck that halt the deletion actually come from a piece of sql. So we may not need to bring in any new sql query, instead I will do some test and see if we can solve the problem with Hibernate only. Youjun On Wed, Mar 24, 2010 at 10:27 AM, youjun guo <you...@ya...> wrote: > In theory making it 100% Hibernate should solve the problem, and should >> also make it consistent with the Hibernate ORM tier for data access. The >> more straight SQL we have in there, the more maintenance problems or risks >> we have down the road. Why does a pure Hibernate solution not work here? >> Hibernate is perfectly capable of orchestrating cascading deletes. > > >> >> -hilmar >> >> >> > |