I had a musing while reading:
http://news.com.com/2100-7344_3-6063599.html?part=rss&tag=6063599&subj=news
where it reminded me of one of MySQL's features:
MySQL's database is built so that it can use a range of different
storage mechanisms, tuned for different purposes, such as
transactions or indexing large amounts of text.
"Rather than have one perfect engine, it's better to have a
pluggable architecture," Urlocker said. "The idea is you can mix and
match within a single application because data will be used in
different ways."
Perhaps adding the appropriate bindings to MySQL to register sqlite as a
storage mechanism would
allow the use of Sqlite in a network environment with out bloating the
core Sqlite code?
Maybe the above makes no sense, but I find the notion appealing that
Sqlite could remain as tight little sql engine but could use the
"network server"
of MySQL should ever such a thing be needed.
Would that be possible?
