Apache OpenOffice (AOO) Bugzilla – Issue 12994
Searching strings in a table not functional via the UI
Last modified: 2006-05-31 14:29:06 UTC
Hi, I've been trying to search strings in my data in both dbase tables and mysql tables, using the binocular button available in the DSB. I enter a string that I know is in the database, e.g. a text string, and ask it to search for the string. The program iterates through the records but shows no result. This has been working perfectly for me ever since I started using StarOffice back in 3.1, and then also when I switched to OOo. Did it get broken during the build ? Alex.
Further comments : This search function is behaving pretty weird : - sometimes it will return a value and the correct one is displayed. - sometimes it will not find anything even though the data is present - sometimes it goes into an infinite loop, cycling through the records without stopping, the only way being to click on cancel I might add that the searches were all carried out on text fields, using the option to search for any data that contained the character (so I wasn't doing any fancy stuff like identical matching or case matching). Uh oh. Alex
Alex, can you please try traveling through the data by simply pressing "next" repeatedly? Do I assume right that in this case, records are skipped?
OK Frank, I tried this : Dbase table. Search for text : USA entered into dialog. Chose the single text field COCOUNTRY to search through in the pull-down menu list. Settings : position "anywhere in the field". THen clicked on search. The data set returns works for three results in a row, on the fourth it shows a result containing "VIETNAM". Continuing searching with same term "USA" brings up results that are correct, then "Great Britain", "Canada". However, although erroneous results are displayed (see my display bug submission as I think it's linked), if you navigate to the record number by getting the screen to redraw, the underlying record shows the correct result with the country being USA. Does that make things clearer for you ? Alex
Frank, I take back the last bit that I said about the underlying record being correct. Just tried on other records with another field, the underlying record identified as meeting the search criteria is wrong. I searched for the string "chris", and it gave me "bruce".
Created attachment 5442 [details] search db results wrong/malfunctioning
sorry, I'll try to be more gossipy .... It was not that I did not understand your explaination, I just wanted to confirm a suspicion I have (without installing the version myself). The point is that there was a bug which produced wrong search results, as well as wrong traveling in the table view. Thus I asked for something completely unrelated to the searching: If you press the "next record" button in the table control continuously, then I suppose that some records will be skipped. Both the skipping and the wrong searching were the result of the same bug. Thus I asked if the skipping happens for you, too, because in this case I know that OOo 1.1 Beta would have been shipped with the bug in question. I admit I did not remotely make this clear with my question :), sorry. Anyway, thanks for the explanation, I am going to install the 1.1 Beta myself, too. Thanks.
confirming. could reproduce it with 1.1 Beta as well as SRX644m9, on windows. targeting + changing OS/platform FS->OJ: to reproduce it: create an LDAP data source which is based on the our internal Sun corporate LDAP server, set the record limit to 500, display the "LDAP directory" table in the data source browser. Search for "chris" in the column "display name". When the second occurence is found, then the highlight table is position in the wrong row. Funnily: The search dialog displays "114" as the record number where the string has been found, the data source browser is scrolled to position 118, and in real, the recod number 116 contains the search string. Seems that the row set and the clone are not really in sync anymore, or something like this. Not sure, though, if this bug is the same as the internal bug #108617# - doesn't really sound this way, but who knows.
Fixed in CWS_APPS61BETA2
Please verify.
*** Issue 13618 has been marked as a duplicate of this issue. ***
fixed
verified in internal build
verified
Hi this issue is fixed in OOo 1.1 Beta2 which is available at http://www.openoffice.org/dev_docs/source/1.1beta2/. I close this bug now. Bye Marc
change subcomponent to 'none'