Wrapped transaction occurring when using GORM?

The GORM library already uses transactions by default for write operations: https://gorm.io/docs/transactions.html.

Does this mean that when using `crdbgorm.ExecuteTx` the GORM transaction is being wrapped in the CRDB transaction?

If that is true, GORM allows for disabling that behavior with the `gorm.Config.SkipDefaultTransaction` field, so perhaps it should be encouraged when using `crdbgorm`, or a new `crdbgorm.Execute` method could be added that does not use a transaction.

Start by reading the issue's GORM transactions documentation link and inspect how crdbgorm.ExecuteTx is used. Compare that behavior with gorm.Config.SkipDefaultTransaction, then determine whether the desired outcome is guidance for users or a separate crdbgorm.Execute method; done means the transaction behavior and recommended approach are clearly established.

Written by the indexing model from the issue text.