You wrote:
"a) They are not portable at all. Moving to another database means rewriting all of them."
I do not agree.
1. Oracle PL/SQL is very similar to PostgreSQL PL/pgSQL in grammar. Almost all RDBMS knows some pl/sql.
2. The new direction: pl/java. the greatest commercial RDBMS products support it. ok the manner is incompatible, but the logic itself is portable. I am working on the free implementation of pl/java for Postgres (which is not a garantee it will ever work:).
Anyway, moving to another database happens realy so often?
Slashdot Mirror
You wrote: "a) They are not portable at all. Moving to another database means rewriting all of them." I do not agree. 1. Oracle PL/SQL is very similar to PostgreSQL PL/pgSQL in grammar. Almost all RDBMS knows some pl/sql. 2. The new direction: pl/java. the greatest commercial RDBMS products support it. ok the manner is incompatible, but the logic itself is portable. I am working on the free implementation of pl/java for Postgres (which is not a garantee it will ever work :).
Anyway, moving to another database happens realy so often?