Find, Find Next on an index, in SQL?
Well your 15 years of using LIKE tells me tons, thanks.
My server size? Ha ! I’m on a Mac laptop and that’s it. There is not yet one client. I am starting out on learning SQL that’s all. I’m writing an app that’s intended to be my demo of my abilities once I get started, in a year maybe, on getting a client. I have no server. I’m using Postgres’s Mac app server to develop with. Small fry here, just a newbie to SQL. Know Omnis, don’t know SQL. I’m planning on servicing smaller companies so that I can remain a lone developer. Thank you for your answers. You’re very kind.
> On Feb 6, 2018, at 12:42 PM, Alex Clay <email@example.com> wrote:
> On Feb 6, 2018, at 15:34, Das Goravani <firstname.lastname@example.org> 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:email@example.com