Chris wrote:
>
> John Thorhauer wrote:
> > If you are not looking to spend time exploring the flexibility/power
> > that turbine offers for you to implement solutions that are taylored
> > specifically to your situation then maybe mysql would be a better fit.
> > I think that you should probabaly decide if your project requires
> > postgres functionality. If not then why not just use mysql? It seems
> > to be used by a lot more developers on this list than postgres.
>
> I can't believe anybody trusts a non-logging db for a website.
> http://openacs.org/philosophy/why-not-mysql.html
I can't believe that people can really be convinced that they need all
the extra shit described in that tired old paper. It makes sense in
certain contexts (billing systems, etc.), certainly, but not for your
run of the mill web app.
--
Daniel Rall <[EMAIL PROTECTED]>
http://collab.net/ | open source | do the right thing
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
