Noah Kantrowitz wrote: >> d) Don't have to write SQL. >> >> This is a BIG one. Makes it easier for those not steeped in SQL to >> have >> a hand at writing plugins. When it comes down to it, writing SQL just >> plain sucks. Writing SQL that all DBs support sucks even more. >> > > I think this is a foolish goal. People unwilling to learn SQL probably won't > want to learn the Trac API anyway. You don't need to interact with SQL for > most Trac plugins either, just stuff that has to store its own data. Given > that this is really the only advantage of an ORM, I would therefore > postulate that an ORM isn't helpful to us.
On the contrary. Perhaps those not willing to learn SQL aren't going to crate database touching plugins. However, I find using the ORM much easier and faster than writing my own SQL. Sure, I know how to write SQL, but if I don't have to, then that's a big win for me. Additionally, I think using the ORM makes the code look nicer rather than having some huge SQL statements embedded in the components. -John --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
