Harald wrote: >> protection of database code, etc. > Are you saying that the fact that the source isn't legally available > to the population at large is a feature? If you are, it's an argument > for security by obscurity, a system with a lot of deep known flaws. > That would be more the "Oracle stored procedures can be encrypted." Which is an argument for ISVs, as they can easier force their customers to pay > "software maintainance". > With open code, clients could buy support from others, who may be cheaper or, even more dangerous, more qualified. > As long as the disease of "Intellectual property" is running around, that "I can encrypt my code" will provide some felt benefit for PHBs.... I have to disagree here. Encrypting stored procedures is not just about forcing customers to pay software maintenance. For us, it's about *protecting hard work and intellectual property*. For example (very recent), we designed a fairly complicated inventory system using PL/pgSQL for a web platform. This customer is now looking into using Microsoft Dynamics CRM. This customer is looking for quotes from other companies to integrate their web platform (pgsql) with the CRM. What now prevents these other companies from stealing our inventory system and putting it into MS SQL server? And better yet, using the inventory system and selling it to other customers? Luckily copyright offers protection, but as we all know some companies always tend to stretch the rules as far as they can. For me, "Oracle stored procedures can be encrypted." is a very real and valuable argument. It would certainly be a valuable feature in pgsql (in the enterprise space).
