M
marian.edu
Guest
This is what we usually call UPSERT, or INSERT ON DUPLICATE KEY UPDATE. Either way there is no need for WHERE clause there, something along the line of… CREATE xxx ASSIGN … ON DUPLICATE KEY UPDATE. This means the CREATE/ASSIGN is a single statement like the SQL INSERT, I would use MERGE instead of ON DUPLICATE KEY UPDATE or just make an UPSERT statement since we have a 4GL (I’m a slow typer). Otherwise fail to see how FIND WHERE … MISSING: END MISSING. is so much better than what we have FIND WHERE … IF NOT AVAILABLE DO: END. I mean, even for a slow typer like me this isn’t really a big improvement 
If you imply that inside the MISSING block there should be an automatic creation of the buffer record and assignment of fields used in where clause then at least there will be some indication about this processing like a ON MISSING CREATE. The missing block will be a transaction block, with error handling and we can have any 4gl code there? (like starting a new dialog maybe) Marian Edu Acorn IT www.acorn-it.com www.akera.io +40 740 036 212
Continue reading...
If you imply that inside the MISSING block there should be an automatic creation of the buffer record and assignment of fields used in where clause then at least there will be some indication about this processing like a ON MISSING CREATE. The missing block will be a transaction block, with error handling and we can have any 4gl code there? (like starting a new dialog maybe) Marian Edu Acorn IT www.acorn-it.com www.akera.io +40 740 036 212Continue reading...