$primaryKey forcefully 'needs' to be auto_increment

[fefo-p]

Describe the bug
The primary key of my table is a combination of numbers and letters.
Using or not validation, a new record will not be saved to DB using Entities' save()

CodeIgniter 4 version
CodeIgniter Version: | 4.0.0-beta.4

Affected module(s)
Couldn't figure it out.

Expected behavior, and steps to reproduce if appropriate
A new record should be saved provided I include the primary key value.
Validation rules take care of it being a unique value.
$numero's format is ##-#####/## (12-34567/89)

https://pastebin.com/embed_js/Dz6JFnmk

Context

• OS: Ubuntu 18.04.2 LTS
• Web server Apache/2.4.29 (Ubuntu)
• PHP version 7.2.19

[tada5hi]

The reason for this is when you Provider the Primary key the Save Method tries to perform an Update. So the Model Should Provide an Option to specifiy if the primary key is Auto inctementing. Fernando P <notifications@github.com> schrieb am Di. 13. Aug. 2019 um 00:26:

…

*Describe the bug* The primary key of my table is a combination of numbers and letters. Using or not validation, a new record will not be saved to DB using Entities' save() *CodeIgniter 4 version* CodeIgniter Version: | 4.0.0-beta.4 *Affected module(s)* Couldn't figure it out. *Expected behavior, and steps to reproduce if appropriate* A new record should be saved provided I include the primary key value. Validation rules take care of it being a unique value. $numero's format is ##-#####/## (12-34567/89) https://pastebin.com/embed_js/Dz6JFnmk *Context* - OS: Ubuntu 18.04.2 LTS - Web server Apache/2.4.29 (Ubuntu) - PHP version 7.2.19 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2133?email_source=notifications&email_token=ADENSBTDEKDXNW3BBXXFWQLQEHPR7A5CNFSM4ILFQMOKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HE2LORA>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADENSBV3ZUQSI6ITPNVEUITQEHPR7ANCNFSM4ILFQMOA> .

[fefo-p]

But, I do have a primaryKey to check if record exists or not. So save() method should be able to figure it out.
I don't see the need for it to be auto incrementing. Maybe just to return the "new id" once inserted into the DB. But that has another workaround

[MGatner]

That's the nature of save() - if it detects a primary key it assumes an update, otherwise it inserts. See https://github.com/codeigniter4/CodeIgniter4/blob/develop/system/Model.php#L529

If you need to force an insert (e.g. when your primary key doesn't exist) use insert(). I think any other approach would require an additional database call which would cripple the convenience of the save() shorthand.

[lonnieezell]

Sorry, that's not how the convenience function of save is meant to work, as @MGatner pointed out. Using insert and update separately will work fine for you, though.