I wonder if the field id is not actually named id but uid or something else, does the lib works as expected?
Because I expected when saving a new record that the save() method looks for if the record was already present in the database and in this case make a UPDATE query and not an INSERT query. The thing is in my case it's happening I get an error because joli tries to insert a row already existing and I wonder if that's because my field id as for name uid.
Could you give me an example showing how should users update a row in the database with convenient method like save.
It wont work from what I've found, I've actually modified the joli core so it alloys when defining your model to set model.primary_key so everywhere then uses that. I recommend this for you if its a requirement!
Hello Xavier, thanks for sharing this.
I wonder if the field id is not actually named id but uid or something else, does the lib works as expected? Because I expected when saving a new record that the save() method looks for if the record was already present in the database and in this case make a UPDATE query and not an INSERT query. The thing is in my case it's happening I get an error because joli tries to insert a row already existing and I wonder if that's because my field id as for name uid.
Could you give me an example showing how should users update a row in the database with convenient method like save.
Thanks for your help and time.