Among RDBMSs, I personally prefer Postgres too, for many of the reasons mentioned - quality of build and add-ons, platform availability, SQL compliance, optional commercial support, Oracle compatibility.
But another factor to consider is deployment on IaaS/PaaS options. Heroku and OpenShift can provision Postgres and MySQL; Google App Engine and PythonAnywhere only provide MySQL. PythonAnywhere is a terrific option; I'm a bit surprised they don't offer Postgres. Maybe someone with influence on the PythonAnywhere folks can give them a nudge? Could push many projects their way. On Thursday, March 7, 2013 4:36:29 PM UTC-5, Richard wrote: > > Also you should consider that DAL adapter are not all equal on quality, > quality for a given adapter is "correlated" to the user base for a given > (my interpretation) and since Postgres is largely used it adapter is really > good. Notice that there is two adapter for postgres psycopg2 and pg8000 the > former is much better then the latter that is still experimental I think. > > Richard > > > On Thu, Mar 7, 2013 at 4:15 PM, BlueShadow <kevin....@gmail.com<javascript:> > > wrote: > >> Thanks Richard. >> Postgres >> Pros: Many User in web2py, open source >> Cons: Speed >> >> MySQL >> Pros: Speed >> >> >> On Thursday, March 7, 2013 9:57:48 PM UTC+1, Richard wrote: >> >>> Postgres, full open source, supported by a consortium, commercial >>> support available (ex.: Enterprise DB), build-in Foreing key constraint, PL >>> SQL (so you can migrate to Oracle), Still with commercial build you are >>> still at one/ten the price of Oracle DB... >>> >>> Also, I think many serious web2py user here are using Postgres. >>> >>> You will have Cons about speed... And Pros for MySQL for the inverse >>> (MySQL speedier). >>> >>> The rule of thumd is, if you need speed on retreiving information (you >>> mostly do select query) go with MySQL. It is reputed faster on select. >>> >>> Richard >>> >>> >>> >>> >>> >>> >>> On Thu, Mar 7, 2013 at 3:41 PM, BlueShadow <kevin....@gmail.com> wrote: >>> >>>> Hi guys so I learned that using SQLlite for me wasn't a great >>>> choice(thanks Niphlod). But since I started using databases when I started >>>> to use web2py. I got no clue what database to use. I used sqllite because >>>> it was in the welcome app and it worked while having my site offline and >>>> with me being the only user. I know the choice is mostly personal >>>> prefrence >>>> but I thought give it a trail and ask you guys why you chose your >>>> particular database. >>>> It would be really nice if you could tell me a few pros and cons. >>>> I researched a little on PostgreSQL, MySQL and SQLite the informations >>>> I got were sometimes contradicting. >>>> I got about 2 times a writing command per page per visit. (keeping >>>> track of views for articles) but apparently thats already too much for >>>> SQLite. >>>> >>>> -- >>>> >>>> --- >>>> 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<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 <javascript:>. >> 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.
