MySQL Masters and Commanders

[YosemiteSam]

Since it's dead in this forum, I've got a question for you. Well, since there at least appears to be some technically savvy Cowboys fans here. (some, not so much even though they think otherwise!)

If you have a product (major system) running MySQL. With Oracles acquisition of Sun and therefore MySQL and since Oracle is known to pretty much axe murder most of the products it has purchased. (PeopleSoft, BEA, etc) What are your plans for your current MySQL instances moving into the future?

It's a little to soon for me to make that decision. I'm not clear on what Oracle will do with it, but even then. It appears Michael Widenius is actually going to fork MySQL. Sure, he has been working on MariaDB, but it wasn't an actual fork. More of an extended version of MySQL. It appears now that he going to fork it and take a lot of current MySQL developers with him. Thats all fine, but I'm not sure he is in a position to support MySQL the way MySQL AB was supporting MySQL prior to it's sell to Sun.


btw, yes I know BEA isn't dead. ...yet

 

[Yeagermeister]

We used to have an accounting package that use MySQL but we replaced it and converted it to pure SQL.

 

[Dallas]

We used to have an accounting package that use MySQL but we replaced it and converted it to pure SQL.

Please don't comment. You are one of the...

"(some, not so much even though they think otherwise!)"

 

[Yeagermeister]

Please don't comment. You are one of the...

"(some, not so much even though they think otherwise!)"

We were forced to upgrade after a fire took out most of our servers.

 

[YosemiteSam]

Please don't comment. You are one of the...

"(some, not so much even though they think otherwise!)"

:laugh2:

mysql>SELECT user FROM CowboysZoneUsers WHERE TechnicalSavvy = 'Not so much';

+---------------+
| user          |
+---------------+
| Yeagermeister |
+---------------+

:

 

[PosterChild]

:laugh2:

mysql>SELECT user FROM CowboysZoneUsers WHERE TechnicalSavvy = 'Not so much';

+---------------+
| user          |
+---------------+
| Yeagermeister |
+---------------+

:

Gawd i'd hate to see where i am in that table.

 

[Yeagermeister]

:laugh2:

mysql>SELECT user FROM CowboysZoneUsers WHERE ******* = 'You betcha';

+---------------+
| user          |
+---------------+
| NYC |
+---------------+

:

Imagine that :laugh2:

 

[Meat-O-Rama]

Since it's dead in this forum, I've got a question for you. Well, since there at least appears to be some technically savvy Cowboys fans here. (some, not so much even though they think otherwise!)

If you have a product (major system) running MySQL. With Oracles acquisition of Sun and therefore MySQL and since Oracle is known to pretty much axe murder most of the products it has purchased. (PeopleSoft, BEA, etc) What are your plans for your current MySQL instances moving into the future?

It's a little to soon for me to make that decision. I'm not clear on what Oracle will do with it, but even then. It appears Michael Widenius is actually going to fork MySQL. Sure, he has been working on MariaDB, but it wasn't an actual fork. More of an extended version of MySQL. It appears now that he going to fork it and take a lot of current MySQL developers with him. Thats all fine, but I'm not sure he is in a position to support MySQL the way MySQL AB was supporting MySQL prior to it's sell to Sun.


btw, yes I know BEA isn't dead. ...yet

I only use MySQL for personal projects, but if it was to go away, I'd likely switch to using Postgresql which is also free and open source.

 

[Khartun]

:laugh2:

mysql>SELECT user FROM CowboysZoneUsers WHERE TechnicalSavvy = 'Not so much';
 
+---------------+
| user          |
+---------------+
| Yeagermeister |
+---------------+

:

HAHA, that is pretty good.

 

[Khartun]

I only use MySQL for personal projects, but if it was to go away, I'd likely switch to using Postgresql which is also free and open source.

PostgreSQL would be the best free source option, imo. PHP supports it. I used both MySQL and PostgreSQL in the past.

 

[YosemiteSam]

PostgreSQL is good stuff. I've used it several times, but not recently. I used it in the past because MySQL didn't have transactions or I couldn't afford ISAM corruption that sometimes happen in MySQL, but that is no longer the case. I would say the best thing about PostgreSQL vs MySQL, is that is scales better beyond 8 CPUs.

What I like about MySQL vs PostgreSQL is the fact that everything is simple. Our replication, system management, and many other things is just so much easier in many cases.

When I've needed very high end requirements, I've always used Oracle in those cases rather than PostgreSQL. With MySQL having InnoDB and all it has to offer, it kind of squeezed PostgreSQL out of that middle ground.

 

[Meat-O-Rama]

PostgreSQL is good stuff. I've used it several times, but not recently. I used it in the past because MySQL didn't have transactions or I couldn't afford ISAM corruption that sometimes happen in MySQL, but that is no longer the case. I would say the best thing about PostgreSQL vs MySQL, is that is scales better beyond 8 CPUs.

What I like about MySQL vs PostgreSQL is the fact that everything is simple. Our replication, system management, and many other things is just so much easier in many cases.

When I've needed very high end requirements, I've always used Oracle in those cases rather than PostgreSQL. With MySQL having InnoDB and all it has to offer, it kind of squeezed PostgreSQL out of that middle ground.

PostgreSQL has always been a couple of steps ahead as far as capabilities, but MySQl has always been a nice lightweight piece of the LAMP stack which I've grown to know and love.

For anything critical though, I always go with Oracle.