Symphony.

I have a field extension that is currently utilizing Symphony::Database()->update() to update a field. I need to fix a bug so that a new row is added to the table if one doesn't exist for that entry (i.e. affects existing Symphony entries). I'm not sure which is the best approach:

1. Check for existing row and execute update if it exists, otherwise create a new row.
2. Delete any existing row and create a new row.

Is there a preference or best practice here?

Usually I use insert - with update set to true. If you would know/set the id/pk that is.

Usually I use insert - with update set to true. If you would know/set the id/pk that is.

Exactly what I needed. I overlooked this at first, but further investigation into MySQL's ON DUPLICATE KEY UPDATE and it became clear.

Cheers!