提示: 作者被禁止或刪除 內容自動屏蔽

TOP

提示: 作者被禁止或刪除 內容自動屏蔽

TOP

提示: 作者被禁止或刪除 內容自動屏蔽

TOP

不如話mybatis (我未寫過) 最快。
Flower 發表於 2013-10-10 15:55


Sure.

But you always mentioned hibernate. Just wanna state that hibernate is not the best JPA implementation out there.

As a matter of fact, my previous company dumped hibernate for PL/SQL because hibernate is just too slow for massive data.

TOP

提示: 作者被禁止或刪除 內容自動屏蔽

TOP

呢方面重未試過喎, 我有機會 DUMPED 返 ORACLE TERSTING 都好喎。你問題是否係

  hibernate pl sql ...
Flower 發表於 2013-10-10 16:08


Basically, convert the update calls which may affect lot of rows into a PL/SQL function/procedure.

And call it from the EntityManager. Any JPA implementation can call stored procedure.

Hibernate generated way more SQL than necessary.

TOP

提示: 作者被禁止或刪除 內容自動屏蔽

TOP

睇下得唔得,
Flower 發表於 2013-10-10 16:29


Using EntityManager.createNativeQuery is more than enough.

http://docs.oracle.com/javaee/6/ ... java.lang.String%29

TOP

提示: 作者被禁止或刪除 內容自動屏蔽

TOP

提示: 作者被禁止或刪除 內容自動屏蔽

TOP