 //: The resulting code is not as streamlined as usual GRDB code, but we could
 //: already do what we needed without much effort.
 //:
-//: ## Custom Protocol: MyDatabaseDecoder
+//: ### Custom Protocol: MyDatabaseDecoder
 //:
 //: In the rest of this playground, we will define a **new realm of requests**.
 //:

//: customization freedom.
//:
//: To end this tour, let's quickly look at two other possible customized
//: row decoding strategies:
//:
//: - Your application needs to decode rows with a context: each decoded value
//: should be initialized with some extra value that does not come from
//: the database.
//:
//:     In this case, you may define a `ContextFetchableRecord` protocol, and
//:     derive all other fetching methods from the most fundamental one, which
//:     fetches a cursor from a prepared statement (as above):

protocol ContextFetchableRecord {
    associatedtype Context

        }
    }
    
    // Define fetchAll, fetchOne, and other extensions...
}
