-
-
Notifications
You must be signed in to change notification settings - Fork 224
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Support for WHEN NOT MATCHED BY SOURCE for MERGE statement [CORE6448] #6681
Comments
Modified by: Leonardt (lxo)security: Developers [ 10012 ] => |
Modified by: Leonardt (lxo)description: It would be very useful to have the option "WHEN NOT MATCHED BY <SOURCE>/<TARGET>" for "MERGE statements". Use case and example of how to use this in Firebird: I currently need this for mass copying. Without the merge statement I would first have to delete everything from the target and then insert it. I see this new feature as very useful for such purposes. Therefore I don't understand why the request in a ticket was rejected years ago (CORE2515) => It would be very useful to have the option "WHEN NOT MATCHED BY <SOURCE>/<TARGET>" for "MERGE statements". Use case and example of how to use this in Firebird now without "WHEN NOT MATCHED BY <SOURCE>/<TARGET": I currently need this for mass copying. Without the merge statement I would first have to delete everything from the target and then insert it. I see this new feature as very useful for such purposes. Therefore I don't understand why the request in a ticket was rejected years ago (CORE2515) |
Hello, is this being considered for implementation in Firebird 4? |
It is too late to consider new features for Firebird 4, sorry. |
Could you please test it in next Firebird 5 snapshot? |
First tests look good so far. Seems to work. |
Submitted by: Leonardt (lxo)
It would be very useful to have the option "WHEN NOT MATCHED BY <SOURCE>/<TARGET>" for "MERGE statements".
Like for example in MSSQL.
Use case and example of how to use this in Firebird now without "WHEN NOT MATCHED BY <SOURCE>/<TARGET":
https://www.sql.ru/forum/1323218/merge-when-not-matched-by-source
I currently need this for mass copying.
When copying, I would like to take everything from the source, update matches, add new records and delete data not contained in the source from the target.
Without the merge statement I would first have to delete everything from the target and then insert it.
Or "Update or Insert "and then do a delete with "where not exists".
I see this new feature as very useful for such purposes. Therefore I don't understand why the request in a ticket was rejected years ago (CORE2515)
The text was updated successfully, but these errors were encountered: