Re: "ocaml_beginners"::[] De-unifying variant types

> The idea of being "locked in" to free software.  Well, I guess
> PG'OCaml does require PostgreSQL, but that's only because it is the
> only database which has the necessary 'DESCRIBE' statement (which,
> given a statement, parses it and tells you what types it takes and
> returns).  If other databases have it, then you could add support for
> them.

Hi,

Well, if it means that you can't easily plug-out Postgresql and
plug-in another DB, it is a sort of lock-in, even if it is much
softer than the lock-in you get with proprietary products!

But anyway, does the type verification of PG'OCaml go all the
way into ensuring that SQL injection attacks are not possible?
And does it provide also for such things as prepared statements,
and the entire range of SQL statements?  If so, I am willing
to take another look into it...

Cheers,
C.S.