mirror of
https://github.com/meteor/meteor.git
synced 2026-05-02 03:01:46 -04:00
d274d8d7ef
SQLite has a worse-is-better philosophy about automatically converting between different data types, such as strings and floating point numbers: https://www.sqlite.org/quirks.html#flexible_typing This means querying for the string "1.10" in a given column can return rows where the column is actually the string "1.1", since SQLite imagines you might be talking about the number 1.1, rather than the string you actually requested. This "feature" became a problem for Meteor after we published Meteor 1.10, which caused SQLite to return multiple rows for the getReleaseVersion query, including both Meteor 1.10 and Meteor 1.1 (which is ancient, from March 2015). While this behavior seems completely indefensible, the SQLite documentation clearly does not consider it a bug, which forces us to work around the consequences by double-checking the queried results with the filterExactRows helper function.