I'm curious to know why a company would outright ban MySQL and derivatives. Is there a technically valid reason or is it more like "the director hasn't seen a full page ad in CIO magazine"?

disclaimer: I don't know the difference between a database and my toes.

On Sun, Jun 9, 2013 at 1:55 AM, Tom Laermans <tom.laermans@powersource.cx> wrote:

On 9/06/2013 9:49, Adam Armstrong wrote:

On 2013-06-09 01:31, Rob VanHooren wrote:

curious whether anyone's farted around with using MariaDB or *gasp*
PostgreSQL for their install.

MariaDB should work fine, as it's a drop-in replacement for MySQL.

Postgres doesn't work, and likely never will. Our SQL framework was written purely with MySQL in mind, and our schema update process will almost certainly only work on MySQL and compatibles.

None of us know Postgres, and in 7 years we've never had a compelling reason to support it.

But what if your company doesn't approve MySQL -and- all derivatives?!?

I know enough about postgres to not want to know any more about it ;-)

On this excellent sunday I bring you excellent music from Observium's main sponsoring country: http://www.youtube.com/watch?v=YVhS0KBQVjw&feature=youtu.be

Tom

_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

--
Alex Presse
"How much net work could a network work if a network could net work?"