On 3/5/13, Leho Kraav <l...@kraav.com> wrote: > On Monday, March 4, 2013 3:20:28 PM UTC+2, Javier Domingo wrote: >> >> Hi,
:) >> I am looking into trac's code, and I have found that there is no DAL. >> >> It has a very flexible database design, but it is not an efficient design >> for a database that will have lots of queries. >> Javier , I am 80% in favor of doing this . please read my previous message ... >> I have found that it uses hard-coded queries (which is difficult to >> understand how it works), text as primary keys, etc. >> >> I would like to ask why doesn't trac use django (with south for db >> versioning). >> ... because Django came into the scene afterwards , they even use Trac as issue tracker afaicr ;) >> I plan to develop a parallel ticket system as a plugin (as I mentioned in >> previous threads) using as base the original trac.ticket structure, using >> django as a DAL and maintaining the interfaces. >> see SQL Alchemy Trac bridge , and do a similar thing for Trac . [...] > > Hi Javier > > Trac is almost 10 years old. Django (or anything else, Pyramid etc) wasn't > nearly the quality players they are today. Trac is also a web application > framework on its own. It has therefore never needed an outside framework to > perform its job. > +1 -- Regards, Olemis. Apache™ Bloodhound contributor http://issues.apache.org/bloodhound Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+unsubscr...@googlegroups.com. To post to this group, send email to trac-dev@googlegroups.com. Visit this group at http://groups.google.com/group/trac-dev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
