lifetime dancing lessons?
Duke Ganote, June 25, 2008 - 9:46 am UTC
Someone's way too Java-centric. However, if they're willing to pay for Oracle developers to build and maintain a cocoon for them to 'hibernate' in...well, sounds like job security to me!
Hibernate? UGGHH
Tom, June 25, 2008 - 1:52 pm UTC
I had to deal with app developers switching to Hibernate about 2 years back... I still remember the discussions about how great it is (or is not)... and I remember the Formal namespacing dictates of using ID as the PK column name, i.e : Employee.ID instead of Employee.Emp_ID... that alone is not too bad, but all of the other shortcomings, including the crappy SQL it generated from the OR mapping was enough to make me puke. And the best of all was my manager telling me that we weren't allowed to use PL/SQL for ANYTHING since it wasn't "standards based" like Java and Hibernate...
hiberation
Duke Ganote, June 25, 2008 - 4:07 pm UTC
Views without instead of triggers
Gary, June 25, 2008 - 8:55 pm UTC
If it is PURELY column naming standards, views can work perfectly well without an INSTEAD OF trigger.
create table good_name (good_col_1 number, good_col_2 varchar2(10));
create view std_name (id, std_col_1)
as select good_col_1, good_col_2 from good_name;
insert into std_name (id, std_col_1)
values (1,'test');
select * from this_is_a_good_name;
June 26, 2008 - 3:43 pm UTC
true, a view is an excellent way to just "rename" a column
however, I presumed there must have been a reason to use 'code' with instead of inserts. I think they are trying to keep the old system "as it was" and the new framework says "nope, we don't do it that way" and the instead of insert triggers are there to trick the framework into thinking it is actually doing something.