I haven't read the PL/SQL proposal yet so please do not take this as
criticism of the proposal. It is just that I have sometimes wondered (having
used and maintained a couple of them) if there is a real need to invent
another procedural language inside a dbms. Who really needs yet another
language that only works in certain special circumstances? Why not just
adapt an existing language implementation and graft SQL integration into
it? For example in Perl:
sub find_prospects_to_contact ()
# note that sql select looks like a file handle/split() combo to perl
while (<select ($name, $phone) from prospects p,
where prospect.interests ~= /computer/ or /electronics/;
>) {
# some stuff to be done per row
...
if ($should_contact) {
insert into contacts_todo values ($name, $phone);
}
}
Of course there are probably a zillion great reasons why this would be hard
or the wrong thing to do, but still...
Wouldn't it be cool?
-dg
David Gould dg@illustra.com 510.628.3783 or 510.305.9468
Informix Software (No, really) 300 Lakeside Drive Oakland, CA 94612
- I realize now that irony has no place in business communications.