1 |
I use MySQL alot at my Company and we use the Community version. I have |
2 |
found that its just as good as the Paid one which by the MySQL website says |
3 |
the paid one is more stable but I have yet to see any problems. |
4 |
|
5 |
On 1/2/07, kashani <kashani-list@××××××××.net> wrote: |
6 |
> |
7 |
> Ryan Crisman wrote: |
8 |
> > MySQL - Paid (Enterprise Edition), Paid Support |
9 |
> > MySQL Community - Free (Personal Edition), Community Support |
10 |
> |
11 |
> While the above is true it fails to answer the question, "As |
12 |
> DBA/sysadmin what is the actual difference between the two so I can pick |
13 |
> the right one for my workload." At least that's the question I |
14 |
> interpreted the first post as asking. |
15 |
> |
16 |
> Right now the code bases are exactly the same. Going forward it's |
17 |
> not |
18 |
> clear whether I'll be able to compile Mysql Enterprise myself with |
19 |
> support for the Sphinx storage engine which is very fast for full text |
20 |
> searches and a feature I desperately need. Also unclear is if the high |
21 |
> concurrency Innodb thread fixes are going to be implemented in Community |
22 |
> or Enterprise first. Enterprise appears to be the stable branch and will |
23 |
> have changes back ported from Community, but the docs are less than |
24 |
> clear at this point. In any case the issues are a bit more complicated |
25 |
> than where your support comes from at least at the high end. For your |
26 |
> general web-app either would be fine. |
27 |
> |
28 |
> kashani |
29 |
> -- |
30 |
> gentoo-user@g.o mailing list |
31 |
> |
32 |
> |
33 |
|
34 |
|
35 |
-- |
36 |
Ryan Crisman |