Download the PHP package mpyw/laravel-retry-on-duplicate-key without Composer
On this page you can find all versions of the php package mpyw/laravel-retry-on-duplicate-key. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download mpyw/laravel-retry-on-duplicate-key
More information about mpyw/laravel-retry-on-duplicate-key
Files in mpyw/laravel-retry-on-duplicate-key
Package laravel-retry-on-duplicate-key
Short Description Automatically retry non-atomic upsert operation when unique constraints are violated.
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package laravel-retry-on-duplicate-key
Laravel Retry on Duplicate Key 
[!CAUTION] ABANDONED: Due to changes in Laravel v10.29.0, the functionalities of this library have been integrated into the Laravel core, making the library unnecessary in most cases. Therefore, maintenance will be discontinued. From now on, retry processing will be automatically performed in
Model::createOrFirst(),Model::firstOrCreate(), andModel::updateOrCreate(). The only pattern that still has value is forModel::firstOrNew() + save(), but since equivalent processing can be written by yourself, please do not use this library anymore.
Automatically retry non-atomic upsert operation when unique constraints are violated.
e.g. firstOrCreate() updateOrCreate() firstOrNew() + save()
Original Issue: Duplicate entries on updateOrCreate · Issue #19372 · laravel/framework
Requirements
| Package | Version | Mandatory |
|---|---|---|
| PHP | ^8.0 |
✅ |
| Laravel | ^9.0 || ^10.0 |
✅ |
| mpyw/laravel-unique-violation-detector | ^1.0 |
✅ |
| PHPStan | >=1.1 |
Installing
Basic usage
[!IMPORTANT] The default implementation is provided by
ConnectionServiceProvider, however, package discovery is not available. Be careful that you MUST register it inconfig/app.phpby yourself.
| OTHER | YOU |
|---|---|
| SELECT (No Results) |
|
| ︙ | |
| ︙ | SELECT (No Results) |
| ︙ | ︙ |
| INSERT (OK) |
︙ |
| ︙ | |
| INSERT (Error! Duplicate entry) |
|
| Prepare for the next retry, referring to primary connection | |
| SELECT (1 Result) |
Advanced Usage
You can extend Connection classes with RetriesOnDuplicateKey trait by yourself.
Differences from other native upsert implementations
- [8.x] Add upsert to Eloquent and Base Query Builders by paras-malhotra · Pull Request #34698 · laravel/framework
- staudenmeir/laravel-upsert: Laravel UPSERT and INSERT IGNORE queries
These implementations are focused on atomically performing INSERT-or-UPDATE queries. Hence, there are definitely clear differences in usage.
firstOrCreate()updateOrCreate()save auto-increment numbering spaces efficiently.- In contrast,
upsert()always increments the number even if no INSERT occurs and it leads to yield missing numbers. This can be a serious problem if the query is executed frequently. If you still want to go along withupsert(), you may need to consider using UUID or ULID instead of auto-increment.
- In contrast,
firstOrCreate()has clear advantages if its call completes mostly with only one SELECT and rarely with succeeding one INSERT.- In contrast, you must always execute two queries in all cases with
upsert().
- In contrast, you must always execute two queries in all cases with
- As for
updateOrCreate(), there may be extra considerations depending on RDBMS.- For RDBMS other than MySQL,
updateOrCreate()would be better unless its call definitely changes field values on rows.upsert()may ruin thestickyoptimization when the connection has both Reader (Replica) and Writer (Primary) because they assume that all rows narrowed by WHERE conditions have been affected. - In MySQL,
upsert()has no limitations about that. It regards that only rows are affected whose field values are actually changed.
- For RDBMS other than MySQL,
- Be careful that
upsert()never triggers Eloquent events such ascreatedorupdatedbecause its implementation is on Eloquent Builder, not on Model. - Only
upsert()supports bulk insert. It is beneficial if there are a large number of records and you don't need any Eloquent events.
All versions of laravel-retry-on-duplicate-key with dependencies
ext-pdo Version *
illuminate/support Version ^9.0 || ^10.0 || ^11.0
illuminate/database Version ^9.0 || ^10.0 || ^11.0
illuminate/contracts Version ^9.0 || ^10.0 || ^11.0
mpyw/laravel-unique-violation-detector Version ^1.0