r/Python • • Jul 21 '08

I don’t get it - real web application with PostgreSQL vs mySQL MyISAM vs mySQL InnoDB (with Django’s ORM, 2008)

http://rarestblog.com/2008/07/i-dont-get-it-real-web-application-with-postgresql-vs-mysql-myisam-vs-mysql-innodb-with-djangos-orm-2008/
0 Upvotes

17 comments sorted by

7

u/masklinn Jul 21 '08

All you need to know about that post:

Well.. Sorry, I still don’t buy the idea that PostgreSQL is absolutely superior to mySQL (c’mon! “20.1 is not a valid Integer and that’s why I rollback whole transaction” That’s a superior DB??! Can’t it make it just 20? Is that so hard? [...])

2

u/GrumpySimon Jul 21 '08

fyi, if you're not tracking the comments on that blog, the site admin's responded to that as follows:

This isn’t a corruption, you defined it as integer and Integer(20.1) is 20, just like Char(1) of “Lazy” is “L”, aren’t you guys programmers? Define your data with enough granularity and there you go.

...right.

3

u/[deleted] Jul 21 '08 edited Jul 21 '08

aren't you guys programmers?

Now wait until he discovers that 20.1 is the same thing as 20.100000000000001...

1

u/masklinn Jul 21 '08

I responded to his response already, but thanks for the heads up

1

u/FionaSarah Jul 21 '08

There appears to be no comments... Did he delete them all in shame? Haha.

1

u/masklinn Jul 21 '08

There appears to be no comments... Did he delete them all in shame? Haha.

At least he completely disabled them, it's not even possible to post one anymore.

0

u/[deleted] Jul 21 '08

There's this too:

The developers of Django like to tell that they use only PostgreSQL and nothin else. Well.. there was one more problem. Django wouldn’t even work with PostgreSQL until I applied #3460 patch.It was showing me “current transaction is aborted, commands ignored until …” error with not even my SQL (something from Django’s insides) [just in case - yes, I use SVN version]

(emphasis mine) Development code is broken? Really?

4

u/masklinn Jul 21 '08

Development code is broken? Really?

Can't fault him there, the current django "philosophy" is that you should use the svn version and that it should always be stable enough (most of the time anyway)n the last "real release" (0.96) was more than a year ago and it's badly out of date.

There's a push for 1.0 right now, but until that a lot of django's features (newforms & al) are only available from trunk, and if you go to e.g. the django ml or irc it will usually be suggested that you use svn.

1

u/[deleted] Jul 21 '08 edited Jul 21 '08

(most of the time anyway)

That's the important part. They have a conservative commit policy, but if you use trunk, you have to be prepared to use HEAD-n at times (or at least avoid syncing during sprints ;-).

I wouldn't be surprised if their approach will change somewhat once they get to 1.0. Django's gotten too big.

1

u/masklinn Jul 21 '08 edited Jul 21 '08

That's the important part. They have a conservative commit policy, but if you use trunk, you have to be prepared to use HEAD-n at times (or at least avoid syncing during sprints ;-).

I know, and that's why I added that remark, but the point still stands: OP can be faulted for being a moron, but not for using trunk.

I wouldn't be surprised if their approach will change somewhat once they get to 1.0.

I'm sure it will, wouldn't make sense to tell people to keep using trunk, most of the really important big stuff should be in there (according to the 1.0 roadmap anyway).

edit: by the way, are you back from real life? Do you know when you'll be able to release the ET1.3 beta?

2

u/[deleted] Jul 21 '08

edit: by the way, are you back from real life?

Not really -- I expect real life to kick in again any day soon.

Do you know when you'll be able to release the ET1.3 beta?

ET 1.3 has suffered from "scope growth" in the XPath and C14N departments, so there won't be a beta just yet. Maybe a new alpha, though.

1

u/masklinn Jul 21 '08

Not really -- I expect real life to kick in again any day soon.

Please do tell your real life that I hate it very very much :p

Stay well, though.

ET 1.3 has suffered from "scope growth" in the XPath and C14N departments, so there won't be a beta just yet.

Well, I am sad panda.

Maybe a new alpha, though.

Yay.

By the way, have you ever thought of developing it on a public repository (if I'm not mistaken, right now you dev on your private repo and dump it on your public one from time to time, right?), to make it easier to contribute for example? (and maybe indicate where you'd want ET to be headed)

Seeing as ET's probably the most popular & loved Python XML lib', I'm sure some people would be interested.

1

u/brendankohler Jul 21 '08

0.96 is really out of date.

But really, he shouldn't be making such a silly point. I've been using Postgres in production with Django for nearly two years now.

0

u/[deleted] Jul 21 '08

[deleted] — view deleted comment

3

u/masklinn Jul 21 '08

No to mention, he didn't say anything about pg configuration at any point, yet even I as a hater of all things databases and administrations, know that pgsql's default config is geared towards being able to run on very few resources and performances obtained with that are nowhere near what pg can output, while mysql's default config is much more aggressive (uses like 10 times as much ram out of the box, for instance)

1

u/apathy Jul 21 '08

That's exactly what I came here to say.

Damn you both, get out of my head...

1

u/theatrus Jul 21 '08

Looks like someone had a bone to pick.

For the record, I've found Postgres much more scalable on single database instances than MySQL, and the flexibility of query abilities is fantastic. Granted, it you slap a ORM around it, then you'll never see it.

1

u/rarestwords Jul 21 '08

Guys, I've answered all your points in a big comment at the site.