Pete, I don’t get any kind of error message. In fact, the query sort of returns successfully. It just doesn’t return all the results. When running the query I showed earlier, I only get back the value of the wordID field. No other field values are returned.
I do have a a couple admin tools, and the query runs correctly in both of them. I tried it in Valentina Studio, which I believe is using a fairly recent version of SQLite, though I can’t tell for sure as I can’t find a SQLite version anywhere in the app. I also tried SQLiteManger, which is an older version and therefore using an older version of SQLite. So I’m guessing I’ve found a bug in the newer LC SQLite library. I think I’ll go ahead and submit a bug report at this point. I’m not really sure what else to try. Thanks for the help. Chris On Mar 12, 2014, at 11:18 AM, Peter Haworth <[email protected]> wrote: > Hi Chris, > I don;t see anything wrong with the WHERE clause. Do you get any sort of > error message or is it that the results of the query are not what you > expect? > > Do you have access to an SQLite admin tool that uses an up to date version > of the SQLite library? If so, you could try the SELECT directly in it and > see what happens. If it works there, then there's something amiss with > either SQLYoga or LC 6.6 > > With regard to using a different SQL library, I entered an enhancement > request on the QCC (# 11729) a while back to enable loading of different > versions of the SQLite library within LC. It was the subject of some > discussion with Mark Waddingham but so far hasn't been accepted for > implementation. This might be a good case to cite to support it. > > Pete > lcSQL Software <http://www.lcsql.com> > Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and > SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html> > > > On Wed, Mar 12, 2014 at 8:51 AM, Chris Sheffield > <[email protected]>wrote: > >> More info. I don't think there's an issue with SQLYoga here. I'm worried >> that I may have come across a bug either in SQLite itself or in LC. >> >> After my query is completely generated, here is my complete query string: >> >> SELECT wordID, targetWord, questionStem, answer, distractor1, distractor2 >> FROM words WHERE words.wordID LIKE '5-C%' ORDER BY random() LIMIT 1 >> >> The part that's not working in LC 6.6 is the where clause. Does anyone >> familiar with sql see any issues with this? As I said before, the same >> query works just fine with LC 6.5.2 and the older SQLite library. I'm not >> really sure what to do. I need some of the bug fixes in LC 6.6, but I also >> need this query to work. Is there a way to take the older SQLite library >> from 6.5.2 and use that? Should I submit a bug report to RunRev? Not really >> sure what to do at this point. >> >> Anybody have other suggestions? >> >> Thanks, >> Chris >> >> On Mar 12, 2014, at 8:59 AM, Chris Sheffield <[email protected]> >> wrote: >> >>> Thanks for the suggestion James. >>> >>> I followed your and Trevor's suggestion to download the latest version >> and have gone in and changed the line of code that opens a SQLite db. In my >> case, I'm not seeing a connection problem, though, and the problem isn't >> fixed after changing that line of code. I'm getting a connection just fine. >> And some queries are working just fine. But in one place I'm seeing an >> issue where setting search criteria is not working. Specifically, I'm using >> a "begins with" search. If I comment out the code that sets that condition, >> my query works. >>> >>> I'm kind of stuck. I need to use LC 6.6 because it contains some bug >> fixes for issues I was seeing in this app. I'll dig into the SQLYoga code a >> bit more and see what I can find. >>> >>> Thanks, >>> Chris >>> >>> On Mar 11, 2014, at 5:29 PM, James Hale <[email protected]> wrote: >>> >>>> Chris, >>>> >>>> Do as Trevor suggested and download the latest SQLYoga. >>>> >>>> It is no longer password protected so you can modify its handlers. I am >> not at my desk right now but if you find the handler that opens the db >> connection you just need to modify the SQLite case (in the switch >> statement) to handle the new syntax for opening a SQLite connection. >>>> >>>> I hit the same issue and just changed the single line to the new syntax. >>>> >>>> Hopefully Trevor will modify the code to enable the call to optionally >> enable to the extensions. >>>> As I wanted them I just changed the line to the new syntax with the >> extensions enabled. >>>> >>>> James >>>> _______________________________________________ >>>> use-livecode mailing list >>>> [email protected] >>>> Please visit this url to subscribe, unsubscribe and manage your >> subscription preferences: >>>> http://lists.runrev.com/mailman/listinfo/use-livecode >>> >>> >>> _______________________________________________ >>> use-livecode mailing list >>> [email protected] >>> Please visit this url to subscribe, unsubscribe and manage your >> subscription preferences: >>> http://lists.runrev.com/mailman/listinfo/use-livecode >> >> >> _______________________________________________ >> use-livecode mailing list >> [email protected] >> Please visit this url to subscribe, unsubscribe and manage your >> subscription preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode >> > _______________________________________________ > use-livecode mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
