ORM framework applicable if only using VIEWs and PROCEDUREs?

Hello community,

I hope this forum is the right one to post my request.

I wonder if Hibernate or any other "ORM framework" makes sense when using only VIEWs and STORED PROCEDURES.

I want to avoid direct INSERT, UPDATE, .... - statements executed by the "ORM framework" to increase flexibility. I want to be able to change the Table structure (schema) and leave the VIEWs and PROCEDURE names and signatures the same (so the interface for e.g. Hibernate won't be changed).

Is using VIEWs and PROCEDUREs and avoiding using direct statements a common practice?

Please help me and give some hints,

Thanks in advance!

[658 byte] By [rapthora] at [2007-11-27 5:01:53]
# 1

> I wonder if Hibernate or any other "ORM framework" makes

> sense when using only VIEWs and STORED PROCEDURES.

You would be using a layer regardless.

>Is using VIEWs and PROCEDUREs and avoiding using direct statements a common practice?

It is done. "Common" would require measuring it and I don't recall seeing stats on it.

I know I prefer it.

jschella at 2007-7-12 10:19:32 > top of Java-index,Database Connectivity,Java Database Connectivity (JDBC)...