From: | fork <forkandwait(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Generalized edit function? |
Date: | 2011-02-27 00:40:29 |
Message-ID: | loom.20110227T013706-502@post.gmane.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas <at> gmail.com> writes:
>
> On Sat, Feb 26, 2011 at 4:19 PM, Josh Berkus <josh <at> agliodbs.com> wrote:
> > Anyway, if it's ASCII-only, that's a guaranteed way to make sure it
> > isn't taken seriously.
>
> Pre-9.1 levenshtein is ASCII-only, and I think some of the other stuff
> in contrib/fuzzystrmatch still is.
I am only looking at 9.0.3 for levenshtein, so I don't have any thoughts yet on
multi-byteness so far. I will have to figure out the multibyte character work
once I get the basic algorithm working -- any thoughts on that? Any pitfalls in
porting?
> So I have some sympathy with the OP's desire not to burden himself
> with the non-ASCII case if he doesn't need it for his application,
> but
> I also agree with your point that we probably wouldn't accept code
> into contrib that doesn't.
Good to know. I will try to avoid backing myself into an ascii corner.
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2011-02-27 01:06:22 | Re: Native XML |
Previous Message | Josh Kupershmidt | 2011-02-27 00:21:05 | psql: \dg off by one error |