[SOLVED] SQLite3 Zeos Search

[Pe3s]

Hello, I have such a problem with the search. The plan is that after typing in edit, the database is to display the matching names and after deleting it, display everything.

Code: Pascal  [Select][+][-]

1.  ZQuery1.Close;
2.   ZQuery1.SQL.Clear;
3.   ZQuery1.SQL.Add('select * from testtbl WHERE Imie='+QuotedStr(Edit5.Text));
4.   ZQuery1.ExecSQL;  

I can ask for help


Thank you for all your help.
Regards

[korba812]

Try

Code: Pascal  [Select][+][-]

1. ZQuery1.Open;

instead

Code: Pascal  [Select][+][-]

1. ZQuery1.ExecSQL;

[dseligo]

As korba812 said, but also:

Code: Pascal  [Select][+][-]

1.   ZQuery1.Close;
2.   ZQuery1.SQL.Clear;
3.   ZQuery1.SQL.Add('select * from testtbl';
4.   If Edit5.Text <> '' then
5.     ZQuery1.SQL.Add('WHERE Imie='+QuotedStr(Edit5.Text));
6.   ZQuery1.Open;

[Pe3s]

Unfortunately it does not work

[Zvoni]

Use parameters.
another thing might be that you're comparing equality, meaning it has to be an exact match incl. Case
Maybe use "LIKE" instead of "="
Don't forget the wildcards

[balazsszekely]

@Pe3s

Unfortunately it does not work

What exactly does not work? Please be more specific.


PS: See attached project. On Windows you need sqlite3.dll. On Linux please change cnMain.LibraryLocation(form create).

[Pe3s]

does not search data

[wp]

For me dseligo's code is working - see attachment.

[balazsszekely]

@wp

For me dseligo's code is working - see attachment.

Yes it works, but if I understood the OP correctly, he wants to change the list on each keypress. Similar to the Object Inspector's Properties filter.
Also closing then (re)opening the query on each search might not be optimal on large tables. This is why I choose the Filtered/OnFilterRecord property and event.

[Zvoni]

@wp

For me dseligo's code is working - see attachment.

Yes it works, but if I understood the OP correctly, he wants to change the list on each keypress. Similar to the Object Inspector's Properties filter.
Also closing then (re)opening the query on each search might not be optimal on large tables. This is why I choose the Filtered/OnFilterRecord property and event.

Look at my post #4
He checks equality