Missing returning clause overload for execute method

[chwo]

Description

Using the returning(_:) clause in an execute(_:) statement does not compile because the execute(_:) statement is only implemented for void QueryValue.

Checklist

• I have determined whether this bug is also reproducible in a vanilla SwiftUI project.
• I have determined whether this bug is also reproducible in a vanilla GRDB project.
• If possible, I've reproduced the issue using the main branch of this package.
• This issue hasn't been addressed in an existing GitHub issue or discussion.

Expected behavior

There should be an overload of the execute(_:) method so that it can be used with the returning(_:) clause.

Actual behavior

No response

Reproducing project

This can be reproduced by adding these two unit tests into QueryCursorTests.swift:

@Test func insertWithReturningSelf() throws {
    try database.write { db in
        let row = Number(value: 1)
        let result = try Number.insert { row }.returning(\.self).execute(db)
        #expect(result == row)
    }
}

@Test func insertWithReturningColumn() throws {
    try database.write { db in
        let row = Number(value: 1)
        let result = try Number.insert { row }.returning(\.value).execute(db)
        #expect(result == 1)
    }
}

I tried implementing the overload based on the other fetch statements but only got it to work for iOS 17 onwards. So I hope you can take over from here and provide the proper overloads.

@available(iOS 17, *)
@inlinable
public func execute<each Value: QueryRepresentable>(_ db: Database) throws -> (repeat (each Value).QueryOutput)?
where QueryValue == (repeat each Value) {
    try fetchCursor(db).next()
}

SharingGRDB version information

0.5.0

Sharing version information

No response

GRDB version information

No response

Destination operating system

No response

Xcode version information

Version 16.4 (16F6)

Swift Compiler version information

[mbrandonw]

because the execute(_:) statement is only implemented for void QueryValue.

Hi @chwo, this is by design. execute is only for executing queries for which the return value is not important. If you want the value returned from the query you can use fetchOne or fetchAll.

Since this isn't an issue with the library I am going to convert it to a discussion. Please feel free to continue the conversation over there!

[chwo]

Thanks for clarifying. That makes sense on second thought 💡