How can I write an INSERT
doctrine query with option ON DUPLICATE KEY UPDATE
?
相关问题
- php PDO::FETCH_ASSOC doesnt detect select after ba
- sqlyog export query result as csv
- NOT DISTINCT query in mySQL
- MySQL: conduct a basic search
- Why sometimes there is one of more gap(s) in the v
The problem is that this is a MySQL specific problem so it will not be directly covered by Doctrine.
As a comment mentioned, you would need to write a RawSQL Query for this. This would be the easiest way.
If you want it more sophisticated and truely DB independent, look into Events and it's possibilities. Before the actual query is executed, you can check for an existence and if it exists, act accordingly.
An ORM/PHP independent way is to write a stored procedure/trigger that handles this problem database side.
In case this helps, you can extend the query builder to append arbitrary SQL (obviously, this may not work across PDO engines):
I created a doctrine dbal wrapper to do that. It can be used with DoctrineBundle with the dbal wrapper_class option.
https://github.com/iJanki/doctrine-mysql-dbal-extensions
I wrote simple solution for me. Just created AbstractRepository class which is parent class of all Repositories(for example UserRepository) and created next method:
You can use this code like this:
You have three options.
The first option is to drop down to SQL. Then you can use all the features your RDBMS of choice provides. But many programmers don't want to drop down to SQL unless absolutely necessary.
The second option is to lock on a related row in another table. For instance, if the entity you're inserting has a unique key per user, you could do a lock on the user you're inserting/updating the entity for. The problem with this solution is that it doesn't work for root entities like
User
itself because you can't lock a row that doesn't exist yet.The third option is to just catch the duplicate key error/exception. That is, you don't check if a row with a particular key already exists; instead, you just attempt to insert it. If it succeeds, all is good. If it fails with the duplicate key error/exception, you catch it and update the existing row. This solution is the best because it avoids an extra
SELECT
query before each insertion that's a constant overhead for the low probability of hitting a race condition. And it's the best because it works for both root and non-root entities.You can use function like this to build and execute raw sql: