From: | Dave Page <dpage(at)postgresql(dot)org> |
---|---|
To: | Erwin Brandstetter <brandstetter(at)falter(dot)at> |
Cc: | pgadmin-support(at)postgresql(dot)org |
Subject: | Re: Issue in "Find and Replace" |
Date: | 2006-11-03 09:36:49 |
Message-ID: | 454B0DB1.1040905@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Erwin Brandstetter wrote:
> brandstetter(at)falter(dot)at wrote:
>> Trying to find strings starting with ' ' (space) generally fails.
>
> I found that the alleged issue with the leading space was due to the
> option "Whole word" being checked.
> However, there are other, more severe issues:
>
> - Replacing ceases to work after non-latin-1 (or at least after German
> umlauts) characters in the text. Try the following test case:
> '
> foo bar test
> test
> test foo bar
> ö <-- note the umlaut!
> foo bar test
> test
> test foo bar
> '
> Now, try replacing 'test'. Even "backwards" does not work on the part
> after the umlaut.
> In case it matters (which I don't think): I have language "Default" and
> "Read and write Unicode UTF-8 files" in the preferences.
> This issue is _not_ present in the original beta4. Maybe introduced with
> your recent fixes?
Thanks, fixed in SVN.
> - If I try a search "From the top" "Forwards", then close the "Find and
> Replace" window, even edit the SQL script, then open "Find and Replace"
> again, and start a new search (without editing the search text) it does
> not search from the top, but continues to search from the last position
> before closing the "Find and Repalce" window.
> Closing the window should make it forget the last position, IMO.
Also fixed in SVN - thanks.
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2006-11-03 09:50:12 | Re: Accented characters column names not displayed |
Previous Message | Dave Page | 2006-11-03 09:11:35 | Re: enhancement idea: re-establish lost connections? |