Re: [Trac] 0.13 stable release?

2012-03-14 Thread Philip Semanchuk
On Tue, Mar 13, 2012 at 3:38 PM, Remy Blank wrote: > Philip Semanchuk wrote: >> On Tue, Mar 13, 2012 at 11:40 AM, Benjamin Lau >> wrote: >>> You should probably add your voice to the ticket increasing the >>> pressure to actually get this patch included in

Re: [Trac] 0.13 stable release?

2012-03-13 Thread Philip Semanchuk
On Tue, Mar 13, 2012 at 11:40 AM, Benjamin Lau wrote: >> We would like to get the Powers that Be off our backs. Right now, it >> seems like our options are -- >> 1) Install & monkey patch Trac 0.12.3 > > I'll leave the conversation about the 0.13 release to others... but > why don't you just apply

Re: [Trac] Access the SQLite database outside Trac

2010-01-10 Thread Philip Semanchuk
On Jan 10, 2010, at 4:03 AM, Scott Mead wrote: On Sat, Jan 9, 2010 at 2:54 PM, Philip Semanchuk wrote: But the OP was asking about accessing the database from a external process (i.e. not Trac), so how does SQLite's threading model enter into it? Sorry, by 'thread' I w

Re: [Trac] Access the SQLite database outside Trac

2010-01-09 Thread Philip Semanchuk
On Jan 9, 2010, at 1:29 PM, Scott Mead wrote: On Sat, Jan 9, 2010 at 11:08 AM, David Champion wrote: Certainly, it's at $TRAC_ENV/db/trac.db. But you might find yourself more productive as well as upward-compatible to use the Trac API instead. Not only that, but sqlite is a single th

Re: [Trac] Full text search performance with Postgres

2010-01-04 Thread Philip Semanchuk
On Jan 4, 2010, at 6:42 PM, David Huang wrote: > > On Jan 4, 2010, at 2:34 PM, Philip Semanchuk wrote: >> Hi David, >> I could be wrong, but this is more of a generic SQL problem than a >> Postgres problem. You need to find out what columns are being >> accessed &

Re: [Trac] Full text search performance with Postgres

2010-01-04 Thread Philip Semanchuk
On Jan 4, 2010, at 2:42 PM, David Huang wrote: > Hi, I had been running Trac 0.11 with a PostgreSQL database for a > while, and recently upgraded it to 0.11.6. After the upgrade, the > full text search is much slower than it was in 0.11, and while it's > searching, Postgres is using all the