On Oct 1, 2010, at 2:41 PM, Igor Tandetnik wrote: > Rather than hardcoding table range, you can synthesize it directly from > measurement. Something like this:
Yes, very nice. That said, not all problems deserve sophisticated solutions. > Note also that 'end' and 'temp' are keywords in SQL, you'll need to use > different identifiers. Similarly, identifier 'speed' (and others) is used > both as table alias and the column alias - this most likely won't fly. I > didn't fix these issues in the example above, so as not to distract from the > logic, but it needs these corrections before it can actually run. I'll leave > this as an exercise for the reader. Yes, good advise as SQL engines tend to reserve half of the English language for their exclusive use. In practice, SQLite doesn't mind and execute the statement properly. _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
