> w/ || that's fixed in 5.0). However, before I go much futher, I intend > to put together a patch that deals w/ unit testing on alternate > databases. My testing methods thus far has literally been to update a > company instance of trac, and let my coworkers hammer on it a bit. I'd > like something a bit more structured, as well as a nice way to tell if > I'm breaking postgresql or sqlite in the process. I should have that
That sounds seriously good! Great stuff. Regards, Manuzhai _______________________________________________ Trac-dev mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac-dev
