in reply to Re^3: [OT] Why I don't use Mysql for new projects
in thread [OT] Why I don't use Mysql for new projects

It still means you have to be wary about who/what you give access to the DB. For some (most?) apps you'd do that anyway, but others might benefit from a more open policy. What if someone has a legacy app build for 4.x ... the quickest way to get it working is just to set the mode to "traditional". It might be a minor thing, but it's something you simply won't have to worry about with Postgres. (Unless there's a way to disable a mode completely on the server, in which case ignore me :)

  • Comment on Re^4: [OT] Why I don't use Mysql for new projects

Replies are listed 'Best First'.
Re^5: [OT] Why I don't use Mysql for new projects
by perrin (Chancellor) on Jul 10, 2008 at 19:14 UTC
    It still means you have to be wary about who/what you give access to the DB.

    I can't believe anyone would seriously give out write access to their shared database to non-trusted users, and if they did, they'd deserve whatever they get.