Since you need notification of data so quickly, perhaps it would be better to use some type of notification table that indicates when new data is available and a trigger to populate this table. Then you can query SELECT MAX(ID) FROM Notifications which is ridiculously fast.
HTH, Sam ------------------------------------------- We're Hiring! Seeking a passionate developer to join our team building Flex based products. Position is in the Washington D.C. metro area. If interested contact [EMAIL PROTECTED] -----Original Message----- From: idkfa [mailto:[EMAIL PROTECTED] Sent: Monday, January 14, 2008 3:45 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] WHERE SomeColumn IN (@SQLiteParameter) ??? That definitely worked as you described, thank you. However, performance is key for us. We'll need to fire off a query like that at a steady 15hz heartbeat (a WHERE NOT IN actually). Could you suggest a faster equivalent to accomplish such a task? What about dumping the string list into a #TempTable and then firing off a SELECT WHERE NOT IN (SELECT value FROM #TempTable)? R -- View this message in context: http://www.nabble.com/WHERE-SomeColumn-IN-%28%40SQLiteParameter%29-----tp148 08093p14813594.html Sent from the SQLite mailing list archive at Nabble.com. ---------------------------------------------------------------------------- - To unsubscribe, send email to [EMAIL PROTECTED] ---------------------------------------------------------------------------- - ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
