| From: | Sean Chittenden <sean(at)chittenden(dot)org> |
|---|---|
| To: | Ian Barwick <barwick(at)gmx(dot)net> |
| Cc: | pgsql-advocacy(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL <> MySQL: first draft |
| Date: | 2003-09-15 18:25:04 |
| Message-ID: | 20030915182504.GA45649@perrin.nxad.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
> Stored Procedures
> -----------------
>
> Stored procedures are blocks of code stored and executed in
> the database backend. They are typically created in an SQL-like procedural
> language or a fourth-generation language such as Java or Perl.
>
> - MySQL has no support for any form of stored procedure. Implementation
> is planned at an unspecified future date:
> http://www.mysql.com/doc/en/ANSI_diff_Triggers.html
>
> - PostgreSQL provides mature and tested support for function creation
> in SQL and the following procedural languages:
> PL/PgSQL (PostgreSQL's own procedural language, similar
> to e.g. Oracle's PL/SQL)
> Perl
> Python
> Tcl
pl/ruby exists too:
http://moulon.inra.fr/ruby/plruby.html
-sc
--
Sean Chittenden
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2003-09-15 23:10:59 | Way cool article |
| Previous Message | Josh Berkus | 2003-09-15 16:39:19 | Re: PostgreSQL <> MySQL: missing the point? |