wisedog/ladybug: database/gorm.go; 4 LoC

Found a possible issue in [wisedog/ladybug](https://www.github.com/wisedog/ladybug) at [database/gorm.go](https://github.com/wisedog/ladybug/blob/a7c6a8fe0ee2b72102b037bf53304adb52b53f15/database/gorm.go#L203-L206)

Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.

>

[Click here to see the code in its original context.](https://github.com/wisedog/ladybug/blob/a7c6a8fe0ee2b72102b037bf53304adb52b53f15/database/gorm.go#L203-L206)

Click here to show the 4 line(s) of Go which triggered the analyzer.

```go
for _, tc := range testcases {
Database.NewRecord(tc)
Database.Create(&tc)
}

```

Click here to show extra information the analyzer produced.

```
No path was found through the callgraph that could lead to a function which writes a pointer argument.

No path was found through the callgraph that could lead to a function which passes a pointer to third-party code.

root signature {Create 1} was not found in the callgraph; reference was passed directly to third-party code
```

Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.

commit ID: a7c6a8fe0ee2b72102b037bf53304adb52b53f15

Inspect database/gorm.go at lines 203-206 and read the surrounding test setup and GORM calls. Compare the range-loop usage with the analyzer's reported concern, then use the issue reactions to classify it as Bug, Mitigated, or Desirable Behavior.

Written by the indexing model from the issue text.