×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On Thu, Dec 15, 2016 at 2:56 PM, <MichaelQuigley@xxxxxxxxxx> wrote:
Really? What about the following?
where db_column >= :search
Lot's of posts over the years detailing the hoops needed in SQL to do a
position to (and provide the exact functionality you have now). Not
really
worth the effort IMO.
It's not the same. From a SETLL, you can read forward or backward. The
SQL above only allows forward.
If you want to allow seamless (to the user) forward or backward, you've got
hoops to jump through.
It can be done, but there's more effort for no benefit. Just leave it as
native I/O.
If you what to move to SQL, then move to SQL. Forget "Position to" and use
"Starts with" or "Contains" or whatever. Consider distinct sort by
functionality.
So instead of being able to simply position to a customer name, your user
can get a list of customers with State=TX ordered by Zip code for instance.
Charles
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
