Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW
 
PerlMonks  

Re^2: [OT] Why I don't use Mysql for new projects

by Mutant (Priest)
on Jul 10, 2008 at 17:51 UTC ( [id://696764]=note: print w/replies, xml ) Need Help??


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

One problem with the "strict mode" solution is it's set on the client. It means you have to be careful about what clients access the DB, or one misbehaving tool could ruin it for everyone. Altho the improvements are what we've all been asking for, they kind of feel "bolted on", whereas they were fundamental design goals of Postgres from the beginning.

Ultimately, both are good choices though. Open source is about giving us more choice, not less. I think the only thing is some people see the success of MySQL as disproportionate to it's quality, when compared to Postgres. (But maybe it's just an example of "worse is better").

Replies are listed 'Best First'.
Re^3: [OT] Why I don't use Mysql for new projects
by perrin (Chancellor) on Jul 10, 2008 at 17:57 UTC
    It can be changed on the client, but the default is set on the server. Someone would have to intentionally change it in order to have this problem. If a malicious user has access to your database, changing the SQL mode is the least of your worries.

      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 :)

        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.

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://696764]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others goofing around in the Monastery: (3)
As of 2024-03-19 05:02 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found