[Discuss] SQL discussion

[Mike Small]

Doug <sweetser at alum.mit.edu> writes:

> postgres rocks in my opinion.  But I still have a fear: triggers.  It is
> triggers that blur what I view as a database - place for my data, with
> programming, which is to transform the data.  There is no universal trigger
> language.  In postgres, there are a bunch.  The trigger code is not so

This is a problem. The result where I've been working is that things
that would make sense to run in the DB are not.  Instead they're written
in C++ and run on a different machine.  Reams of data gets unnecessarily
copied across the network, just because we needed to support multiple
RDBMes and didn't feel we could afford to have multiple sets of stored
procedures, one for each vendor's language.

-- 
Mike Small
smallm at panix.com