On Wed, Aug 13, 2014 at 7:52 AM, Dmitri Maziuk <[email protected]> wrote:
> On 8/12/2014 7:00 PM, Ryan Ollos wrote: > > I would emphasize again to Jared, unless you have a good reason to >> migrate to PostgreSQL, you are much better off sticking with SQLite. You >> will find fewer problems with plugins when using SQLite. I would go as >> far as to say, if you plan to utilize dozens of plugins and you can't >> fix issues that you'll experience with PostgreSQL on your own, you >> should stick with SQLite. >> > > Might be worth looking into sqlalchemy for the next development cycle... > > Dima Just to be clear, there is not any problem with Trac and it's database API. The issue is that developers don't follow the guidelines for database API usage to make their plugins cross-db compatible. Further, most developers only test with SQLite. http://trac.edgewall.org/wiki/TracDev/DatabaseApi#RulesforDBAPIUsage The ORM could make it less likely that developers make errors when writing database access code, but that would remain to be seen and depend on implementation details. -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
