> doesn't rely on proprietary solutions. no proprietary solution is involved, really, as PostgreSQL is nearly as close to the SQL standard as one gets
> A lot of this work is trying to > reproduce object oriented approaches we aren't reproducing much of anything (in the database, that is) but rather try to avoid falling into the traps I pointed out > Simply use those > solutions rather than trying to figure it out for a given database engine. I take it this is not to mean that I shouldn't rely on transactions, nested selects in where clauses, triggers, stored procedures, foreign keys, views and check constraints either because some deficient database engines don't support them ? Karsten -- GPG key ID E4071346 @ wwwkeys.pgp.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
