Ühel kenal päeval, R, 2006-05-19 kell 11:29, kirjutas Mark Woodward: > > Andrew Dunstan <[EMAIL PROTECTED]> writes: > >> Mark Woodward wrote: > >>> Again, there is so much code for MySQL, a MySQL emulation layer, MEL > >>> for > >>> short, could allow plug and play compatibility for open source, and > >>> closed > >>> source, applications that otherwise would force a PostgreSQL user to > >>> hold > >>> his or her nose and use MySQL. > >>> > >> If we had infinite resources this might make sense. We don't, so it > >> doesn't. There is a real cost to producing a compatibility layer, and > >> the cost will be those spiffy new features. > > > > The real problem is that there's a whole lot of stuff, such as mysql's > > weak error checking, that I don't think a "compatibility layer" could > > sanely provide. > > > I kind of agree with this statement, but while I was playing devils's > advocate and just grousing a bit about having to use MySQL, there is a > sort of reality of "openomics" where mind-share is everything.
Maybe we could have a Google SoC project to strip Postgres of all its useful features (mainly ACID, but also introduce NULL==""==0 and weak foreign keys) to make it MySQL compatible. And if we start locking a table on each update, we can get rid of MVCC altogether and do fast selects, in-place updates and select from indexes only. Then that branch (PostgreSQLite) could be pimped to MySQL users as a way to "support" postgres. Nah, not really useful, but perhaps we could publicize the list of things that would have to go to be compatible :P ---------------- Hannu ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
