You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This happened because the table name is plural already, and singularizeRecordNames is set to false by default. I.e. "talents" already is plural and then clashes with the singular "talents". Changed the fancifier to detect that and deal with the case properly.
When the plural and the singular raw name was the same,
the deduper kicked in and added a `0`, e.g.
```swift
func sqlite3_talents0_fetch()
```
This happened because the `talents` was plural already
(and hence ended up with the same name).
This only happens w/ `singularizeRecordNames` set to
false (the default).
Fixes issue #12.
When generating a DB for this:
The result is mostly OK, but ends up with those SQLite API functions:
Notice the
talents0
, it is probably generated by the code which makes the identifiers unique. The CUD functions are fine though:The text was updated successfully, but these errors were encountered: