John Hampton kirjoitti: > Olemis Lang wrote: >> This is in order to use the ORM. Ok. But my question was actually >> about overriding Trac built-in models by using classes generated by >> the ORM, perhaps using the same or similar schema ;) > > You don't. > >> My doubt is mainly about how to connect Trac (plugins, components, >> ...) with ORM-specific classes, and replace the built-in approach to >> access DBs. AFAIK, Trac models contain hard-coded SQL statements, >> besides instances of plugins rely on self.get_db_cnx() to access the >> database, and not in entity classes (e.g. those provided by ORMs) > > Yes, the different subsystems use SQL directly to access the DB. Any > real mucking that you'd be doing there would be a massive patch to Trac. > > There is a sqlalchemy-ng branch in the sandbox. It has been a bit > neglected, but may be a starting point.
I was asking same thing about half a year ago and Noah gave very good answer why not ORM. And of course you John gave also your opinion.. :D Thread is titled "Elixir and Trac". I'm too lazy to google thread link here. (I use MUA, that's my excuse for being lazy) -- Jani Tiainen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
