Find, Find Next on an index, in SQL?
I prefer readable code first, followed by clever stuff if the performance drops off due to the size of data.
So learn first how to use SQL, and then start to polish and refine it. It took me 2+ years to really let go of Omnis 7 and start to use Studio & SQL so it performed better than the Omnis data file.
So hang in there and be happy that it works at this stage. I was, and still am really.
Mike Matthews, Managing Director, Lineal Software Solutions Ltd
Apple Reseller, Microsoft Partner, SQLWorks Business Partner
phone: 01271 375999 | web: lineal.co.uk | email: email@example.com
> On 6 Feb 2018, at 20:42, Alex Clay <firstname.lastname@example.org> wrote:
>> On Feb 6, 2018, at 15:34, Das Goravani <email@example.com> wrote:
>> Others are telling me strongly to avoid LIKE because it does a whole table search. I like LIKE because it does just what I want, I don’t like whole table searches. I’m not sure who is right, you or them, when it comes to like. Thank you for this clarification below.
> There are plenty of ways to optimize your database queries. I tend to worry about making the code work, then worry about tuning for performance. Of course, don’t write needlessly poor code. Quite the opposite—code that’s clean and east to test and maintain is far better than a tightly optimized pile of spaghetti.
> I don’t know what the size of your datasets or the specs on your servers are. We’ve used ILIKEs for character searches for 15+ years without performance issues.
> Manage your list subscriptions at lists.omnis-dev.com
> Start a new message -> mailto:firstname.lastname@example.org
Manage your list subscriptions at lists.omnis-dev.com
Start a new message -> mailto:email@example.com