Re: Portability, was: using functions to generate custom error messages

<quote who="Josh Berkus">
> Thus, in the abstract, a design relying on triggers and procedures is
> perfectly portable *in concept*, but the actual code would need to be
> re-written for each target platform.

Not only the database code (stored procedures and triggers) needs to be
rewritten, but also application (or front-end) calls to stored
procedures
often need to be rewritten as each database has its way of calling them.

a.

It appears that there is a real need to standardize at least the
interface to procedure calls, so that at least the apps don't have to be
re-written. That way, just as mainstream SQL looks alike but is
implemented differently, stored procedures would be too. Eventually,
perhaps the stored procedures themselves could have standard interface,
so that most of them (at least trivial ones) can be ported w/o
re-writing.

OK, enough daydreaming... :)

r.