FTBFS against sqlite3 3.37 or newer
Bug #1956796 reported by
Dan Bungert
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ruby-sqlite3 (Debian) |
Fix Released
|
Unknown
|
|||
ruby-sqlite3 (Ubuntu) |
Fix Committed
|
High
|
Simon Chopin |
Bug Description
When built against sqlite 3.37 or newer, the build will fail in test.
Example:
https:/
TC_ResultSet#
Expected: ["integer", "text"]
Actual: ["INTEGER", "TEXT"]
+2 more failures of a similar nature.
As of sqlite 3.37.0, with FossilOrigin-Name:
d2da62a9df63036
type names for 5 common types BLOB, INT, INTEGER, REAL, and TEXT will be
treated as if they were created in all uppercase.
Changed in ruby-sqlite3 (Debian): | |
status: | Unknown → New |
Changed in ruby-sqlite3 (Ubuntu): | |
importance: | Undecided → High |
assignee: | nobody → Simon Chopin (schopin) |
status: | Confirmed → In Progress |
Changed in ruby-sqlite3 (Debian): | |
status: | New → Fix Released |
To post a comment you must log in.
Adjust tests for combat with old and new sqlite3.