> One client I worked for had the same idea. They did their entire > eCommerce site in PL/SQL for Oracle. They didn't do it for security, > but because PL/SQL was so versatile. It "rendered" pages, parsed xml, > wrote files, and sent email. It was abandoned because it was so > complicated and fragile that upgrades took forever, and it took 3 > full-time testers to keep bugs (mostly) out of production.
That's really interesting Joe. My first programming job was at Digital River in the 90s and they did the exact thing same. It was cumbersome and slow. But you could make all the db changes you wanted whenever you needed. I left before this happened but they migrated to Java as that was a better business fit. Kevin, my gut says that unless it solves a tricky business problem it will not give a good return on investment. Maybe the client is so paranoid about other issues that wasting money for little value isn't a big deal. *shrugs* Cheers, Marty _______________________________________________ Bdrg-members mailing list [email protected] http://rubyforge.org/mailman/listinfo/bdrg-members
