Hi, I have a bizarre problem. Here is an example of something I tried in sqlite3 3.3.8:
sqlite> select genre,filename from objects where media_type=1; ....query abbreviated... Msica independiente|0056_People Get Ready1_test1.wma POP|0057_The Mighty Ship1_test1.wma POP|0058_The Mighty Quinn1_test1.wma ....query abbreviated... sqlite> select genre,filename from objects where genre='POP'; sqlite> So basically, no results are returned from the second query although clearly there are items in the list with genre='POP'. This problem only happens on Linux. On Windows, the query returns the results as expected... Which makes it yet more bizarre. The exact same query run "in code" using the C interface, rather than on the command line interface, also behaves similarly... Works on Windows, not on Linux. In both cases I am careful to put the entire query into UTF-16, as the strings are stored as UTF-16 for internationalization purposes. I have a couple questions: 1) Would having an index on the genre column cause any potential issues here? 2) Is there a potential issue in string handling between linux/windows that I should be aware of? 3) Are there any build-time configuration differences I may have inadvertently introduced that may cause behavior like this? The Linux version runs on an ARM-11. The Windows version runs on a typical Dell PC in a visual studio environment. Thanks, Brett ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
