On Mon, Apr 25, 2011 at 8:50 PM, Dan McGee wrote:
> On Mon, Apr 25, 2011 at 10:38 PM, elij wrote:
>> On Mon, Apr 25, 2011 at 7:49 PM, Dan McGee wrote:
>>> On Mon, Apr 25, 2011 at 9:35 PM, elij wrote:
* using the limit offset format of `"LIMIT x,y"`
postgresql doesn't support this for
On Mon, Apr 25, 2011 at 10:38 PM, elij wrote:
> On Mon, Apr 25, 2011 at 7:49 PM, Dan McGee wrote:
>> On Mon, Apr 25, 2011 at 9:35 PM, elij wrote:
>>> * using the limit offset format of `"LIMIT x,y"`
>>> postgresql doesn't support this format, so I had to track each
>>> occurrence down and chang
On Mon, Apr 25, 2011 at 8:38 PM, elij wrote:
> On Mon, Apr 25, 2011 at 7:49 PM, Dan McGee wrote:
>> And case sensitivity would come into play, no?
>
> I built the fulltext index as follows:
> alter table packages add column tsv tsvector;
> update packages set tsv = to_tsvector('english', coalesce
On Mon, Apr 25, 2011 at 7:49 PM, Dan McGee wrote:
> On Mon, Apr 25, 2011 at 9:35 PM, elij wrote:
>> While converting the aur codebase from mysql to postgresql (just for
>> fun/to see if I could), I ran into a few mysql specific gotchas, and a
>> few oddities. Here are some of my notes from the ex
On Mon, Apr 25, 2011 at 9:35 PM, elij wrote:
> While converting the aur codebase from mysql to postgresql (just for
> fun/to see if I could), I ran into a few mysql specific gotchas, and a
> few oddities. Here are some of my notes from the experience.
Mind sending the diff along for funzies? Even
