I have been using postgresql years before it had its actual name and I found their statement "The world's most advanced open source database", always true. Not anymore, I think now they could remove the "open source" words. ;-) ;-)
Use postgresql. The people leading a free software project and people behind postgresql have a good score of accomplished results. Compared to other rdbms I see only cons. I think there is no commercial competitor that reaches the same high quality. I would prefer it just for the authorization model, simple and clean. Serial size (was mentioned here)? can be small or really big: http://www.postgresql.org/docs/9.2/static/datatype-numeric.html Speed? Explain guides you to build the indexes as you should. Large datasets? No one can beat postgresql, no not even the commercial monster Cluster support? 9.x series is really easy to configure Documentation? The manual is very well written Stored procedures? Supports python too among zillions of languages XML,JSON support? there And table inheritance, triggers... rule system: http://www.postgresql.org/docs/9.2/static/rules.html what I personally enjoy is: - command completion that works in the shell - the transactional engine which is the most robust I found even compared to commercial ones - the ease in snapshotting/hotcopying databases - robustness in dump/restore procedures The problem for many new users can be how the prepackaged postgresql.conf is written. Many distribution still use a configuration that is for machines with 256MiB of RAM or so, that's hysterical! On the same line many modules are not enabled by default on many distributions, like the system had to be tuned for an embedded platform! Postgresql footprint can be very small if needed, but that is not the average use case need. mic 2013/3/9 LightDot <light...@gmail.com>: > I don't know in terms of user numbers but mysql is getting replaced with > mariadb in Fedora, which will have some impact. > > Current plan for Fedora 19 is this: > - mariadb package will provide "mysql" > - existing mysql package will be renamed to MySQL > - mariadb and MySQL pacakges conflict, they can't be installed at the same > time. > > In others words, mariadb will act as a drop-in replacement for mysql. All > programs built against mysql libs will be rebuilt against the new "mysql" > libs, thus against mariadb. Everybody who installs "mysql" will in fact > install mariadb. > > There has been some debate about this mysql replacement and I'm expecting > further discussions, especially when Fedora 19 alpha and beta get released > and more users become aware of the change. I don't see any real changes for > the users though, at least not in the near future. > > Regards, > Ales > > > On Friday, March 8, 2013 9:39:38 PM UTC+1, Richard wrote: >> >> Thanks Cliff I wasn't about that issue, it's good to know that. >> >> I would be really curious to know if the MySQL user base had splitted >> since the MariaDB fork and what the proportion that stays with MySQL and now >> with MariaDB... >> >> Richard >> >> >> On Fri, Mar 8, 2013 at 3:17 PM, Cliff Kachinske <cjk...@gmail.com> wrote: >>> >>> @Richard >>> >>> Yeah, I know. But what about documentation? >>> >>> The MySQL code itself is free open source, but Oracle owns the copyright >>> on the MySQL documentation. >>> >>> So as the MariaDB fork adds features, the MySQL documentation becomes >>> more and more inaccurate. At some point there will have to be a full >>> rewrite of the MariaDB docs. Just seems too messy. >>> >>> >>> On Friday, March 8, 2013 8:44:52 AM UTC-5, Richard wrote: >>>> >>>> @Cliff MariaDB!! >>>> >>>> :) >>>> >>>> Richard >>>> >>>> >>>> On Fri, Mar 8, 2013 at 7:36 AM, Cliff Kachinske <cjk...@gmail.com> >>>> wrote: >>>>> >>>>> It's not just the legal aspect. >>>>> >>>>> After seeing how poorly Oracle supported OpenOffice, I would be >>>>> concerned about their future support for MySQL as well. >>>>> >>>>> >>>>> On Friday, March 8, 2013 4:43:06 AM UTC-5, Niphlod wrote: >>>>>> >>>>>> This is going nuts. He was fine until now with SQLite, either one of >>>>>> mysql or postgres will do fine, with a total preference on postgres if he >>>>>> doesn't want to employ a legal office to know if he can use mysql or not. >>>>>> >>>>>> PS: the day I'm going to choose mysql over postgres for the combined >>>>>> requirement of having: >>>>>> - a nice syntax to expose an autoincrementing field >>>>>> - is able to accomodate 8M rows with 3 bytes instead of 4 (I'll never >>>>>> consider a tiny or a smallint as an autoincrement-eligible field) >>>>>> it's the day I'll stop working on databases. >>>>>> >>>>> -- >>>>> >>>>> --- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "web2py-users" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to web2py+un...@googlegroups.com. >>>>> >>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>> >>>>> >>>> >>>> >>> -- >>> >>> --- >>> You received this message because you are subscribed to the Google Groups >>> "web2py-users" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to web2py+un...@googlegroups.com. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >> >> > -- > > --- > You received this message because you are subscribed to the Google Groups > "web2py-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to web2py+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
