|Pliant has it's own database engine.
- very well integrated in the HTTP server (no glue code)
- very safe (efficient automatic crash recovery)
- very simple to administrate (consistent access rights)
- trivial engine
- requires much memory
- so cannot handle large databases (more than 2 GB)
- much slower than MySQL for complex requests (guessed from the design)
Now, if you want to interface MySQL from a Pliant program, you have to
deal the MySQL client DLL. Pliant can do that nearly the same way you would
do it from a C program.
At a higher level, you have to chose one option:
- either you use directly the MySQL client library from your application.
- or you interface the Pliant database engine so that it uses MySQL as
it's low level storage engine, and then you also get the advantages
introduced by Pliant database engine, but it's much more work because
you have to dig in Pliant database engine internals.
The last option is one I'm considering, so I may well provide transparent
access to MySQL from Pliant database engine in a few monthes, but nothing