> -----Original Message-----
> From: [email protected] [mailto:[EMAIL PROTECTED] On
> Behalf Of John Hampton
> Sent: Tuesday, October 28, 2008 4:03 PM
> To: [email protected]
> Subject: [Trac-dev] Re: Elixir and Trac
> 
> 
> Noah Kantrowitz wrote:
> > This shares all the same downsides as the existing SA branch. Using
> an ORM
> > provides very little tangible benefit for non-trivial overhead
> general
> > obfuscation.
> 
> I'm not sure this is true.  Unproven, yes, but the more I'm using SA in
> my own projects and actually modeling the Trac schema, the more I think
> that moving to SA IS the eventual right path.
> 
> 
> > The idea of using SA was always just to use it as a cross-DB
> > API, not as an ORM as far as I remember.
> 
> Initial, perhaps, but not always
> 
> > Really the only benefit is some of
> > the common operations in the model classes are autogenerated, but
> those are
> > a) only written once per model anyway, b) easy to cut-n-paste from
> another
> > model, and c) don't change often enough to warrant this kind of
> > complication.
> 
> 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.

--Noah


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to