fix tests

docs/src/tools.md

@@ -74,7 +74,7 @@ The original [MBTiles specification](https://github.com/mapbox/mbtiles-spec#read
 
 A typical Normalized schema generated by tools like [tilelive-copy](https://github.com/mapbox/TileLive#bintilelive-copy) use MD5 hash in the `tile_id` column. The Martin's `mbtiles` tool can use this hash to verify the content of each tile. We also define a new `flat-with-hash` schema that stores the hash and tile data in the same table. This schema is more efficient than the `normalized` schema when data has no duplicate tiles (see below). Per tile validation is not available for `flat` schema.
 
-Per-tile validation will catch individual invalid tiles, but it will not detect overall datastore corruption (e.g. missing tiles or tiles that shouldn't exist, or tiles with incorrect z/x/y values).  For that, Martin `mbtiles` tool defines a new metadata value called `agg_tiles_hash`. The value is computed by hashing  `cast(zoom_level AS text), cast(tile_column AS text), cast(tile_row AS text), tile_data` combined for all rows in the `tiles` table/view, ordered by z,x,y. In case there are no rows or all are NULL, the hash value of an empty string is used.
+Per-tile validation will catch individual invalid tiles, but it will not detect overall datastore corruption (e.g. missing tiles or tiles that shouldn't exist, or tiles with incorrect z/x/y values).  For that, Martin `mbtiles` tool defines a new metadata value called `agg_tiles_hash`. The value is computed by hashing  `cast(zoom_level AS text), cast(tile_column AS text), cast(tile_row AS text), cast(tile_data as blob)` combined for all rows in the `tiles` table/view, ordered by z,x,y. In case there are no rows or all are NULL, the hash value of an empty string is used.
 
 The `mbtiles` tool will compute `agg_tiles_hash` value when copying or validating mbtiles files.
 

martin-mbtiles/src/mbtiles.rs

@@ -564,20 +564,21 @@ where
     let query = query(
         // The md5_concat func will return NULL if there are no rows in the tiles table.
         // For our use case, we will treat it as an empty string, and hash that.
+        // Note that in some weird rare cases, a column with blob type may be stored as an integer value
         "SELECT
-             hex(
-               coalesce(
-                 md5_concat(
-                   cast(zoom_level AS text),
-                   cast(tile_column AS text),
-                   cast(tile_row AS text),
-                   tile_data
-                 ),
-                 md5('')
-               )
-             )
-             FROM tiles
-             ORDER BY zoom_level, tile_column, tile_row;",
+         hex(
+           coalesce(
+             md5_concat(
+               cast(zoom_level AS text),
+               cast(tile_column AS text),
+               cast(tile_row AS text),
+               cast(tile_data as blob)
+             ),
+             md5('')
+           )
+         )
+         FROM tiles
+         ORDER BY zoom_level, tile_column, tile_row;",
     );
     Ok(query.fetch_one(conn).await?.get::<String, _>(0))
 }