the mistake is perfectly understandable. reusable components can really speed up development time and ease maintenance. they just didn't know database architecture. method 4 dynamic sql stored in the database is the best way to go here... i think. these updates may run 250,000 times a day. i'll have to check to see how well dbms_sql works under that level of usage. wasn't a fight. i found it in a code review. everyone was perfectly reasonable. -------------- Original message -------------- > To the barracades, my friends! > > We must stamp out the notion that REUSE is a justification to populate the > world with bad code. > > They want a reusable update handler? Fine. Write a good one and reuse it at > will. Better yet, have someone give you one that already works. > > Guns don't kill people. > GO TOs don't create spaghetti code. > Object handling principals and packages don't justify reuse and propagation > of bad code. > > Bad people can kill people a whole lot easier with guns than without guns. -- //www.freelists.org/webpage/oracle-l