Re: Optional operator index discussion

2012-08-12 Thread Eric Floehr
Hi Russ, Sorry for the delayed response. Just finished up chairing PyOhio and got through my work backlog. Broadly speaking -- yes, sounds interesting; the trick will be coming > up with an API that *isn't* PostgreSQL specific. > Definitely, and one that doesn't complicate things for the 99%

Re: Optional operator index discussion

2012-07-18 Thread Russell Keith-Magee
On Thu, Jul 19, 2012 at 2:19 AM, Eric Floehr wrote: > I'd like to open up a discussion on the possibilities of having a way to > optionally specifying not to create operator indexes on CharField's when > db_index=True. Based on the consensus from this discussion, I'll open up a > ticket and if it

Optional operator index discussion

2012-07-18 Thread Eric Floehr
I'd like to open up a discussion on the possibilities of having a way to optionally specifying not to create operator indexes on CharField's when db_index=True. Based on the consensus from this discussion, I'll open up a ticket and if it is within my abilities, generate a patch. For background