Timeline for INSERT with ON CONFLICT does not insert rows as expected
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 7, 2020 at 19:20 | comment | added | Alex A. | Yeah, these are not assumptions, I tested and retested these things. | |
| Dec 7, 2020 at 17:10 | comment | added | Erwin Brandstetter |
If so, you can as well test with this simpler query: SELECT * FROM listing_master m WHERE NOT EXISTS (SELECT FROM listing WHERE feed_listing_id = m.feed_listing_id) Still missing rows? But are you sure your assumptions are true? Test, rather than just assume. Like Sherlock Holmes said: "When you have eliminated the impossible, whatever remains, however improbable, must be the truth."
|
|
| Dec 7, 2020 at 8:06 | comment | added | Alex A. |
For the last couple of days I am trying to make sense of your answer, and I am not sure I get it. Some things to clarify though: Currently, there is only one feed_id in the system. #2. Since the data is initially coming from an external feed, it is impossible to have duplicate feed_listing_id if it was already deleted.
|
|
| Dec 6, 2020 at 0:05 | history | answered | Erwin Brandstetter | CC BY-SA 4.0 |