 | |
#11
 
| |||
| |||
|
Re: upsert strategies? -
11-12-2008
, 01:30 PM
|
So far, I've figured out 4 possible ways to perform upsert-like functionality: 1. try insert, on exception update 2. try update, on exception insert 3. delete, then insert 4. merge with DUAL It seems so far the nicest solution is #4. Here's some questions: - Do the other methods have any features which might recommend them? - Are there any methods that might be portable to other databases? - Are there any methods I might be overlooking? Many TIA! Mark Search asktom.oracle.com for "upsert" - he has documented, timed |
--
Regards,
Frank van Bortel
#12
| |||
| |||
|
|
So far, I've figured out 4 possible ways to perform upsert-like functionality: 1. try insert, on exception update 2. try update, on exception insert 3. delete, then insert 4. merge with DUAL It seems so far the nicest solution is #4. Here's some questions: - Do the other methods have any features which might recommend them? - Are there any methods that might be portable to other databases? - Are there any methods I might be overlooking? Many TIA! Mark Search asktom.oracle.com for "upsert" - he has documented, timed |
--
Regards,
Frank van Bortel
#13
| |||
| |||
|
|
So far, I've figured out 4 possible ways to perform upsert-like functionality: 1. try insert, on exception update 2. try update, on exception insert 3. delete, then insert 4. merge with DUAL It seems so far the nicest solution is #4. Here's some questions: - Do the other methods have any features which might recommend them? - Are there any methods that might be portable to other databases? - Are there any methods I might be overlooking? Many TIA! Mark Search asktom.oracle.com for "upsert" - he has documented, timed |
--
Regards,
Frank van Bortel
#14
| |||
| |||
|
|
You're better served by writing to the dbms in use, not attempting to generate 'universal' code which likely won't scale nor will it perform. |
--
Sybrand Bakker
Senior Oracle DBA
#15
| |||
| |||
|
|
You're better served by writing to the dbms in use, not attempting to generate 'universal' code which likely won't scale nor will it perform. |
--
Sybrand Bakker
Senior Oracle DBA
#16
| |||
| |||
|
|
You're better served by writing to the dbms in use, not attempting to generate 'universal' code which likely won't scale nor will it perform. |
--
Sybrand Bakker
Senior Oracle DBA
#17
| |||
| |||
|
|
You're better served by writing to the dbms in use, not attempting to generate 'universal' code which likely won't scale nor will it perform. |
--
Sybrand Bakker
Senior Oracle DBA
 |
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.