[TurboGears] Re: why does TG use SQLObject?

[Serge Wroclawski]

Everyone is different, but let me see if I can give you a few reasons why objects make sense for me.

First, using objects is more natural. I'm a Python programmer. SQL is "something else". When I write Python, going to SQL requires a change in mindset. It's a pain I'd like to avoid when I can.

Secondly, for me, I like having the data validation in the object. We all know that you can't rely on client side data validation, and while you can be careful, putting the data validation low, near to the storage, makes it easier.

Third, SQLObject is database independant. I don't need to change (much of) my code even if I change databases. This is a huge win if you prototype with sqlite and move to mySQL.

Fourth, I can use objects in clever ways, for example, to store data that's not in the database in the object and make those distinctions invisible to the application.

That's why SQLObject is a win for me.

- Serge Wroclawski