So I can see why someone might think they need to know the pseudokey, but they are incorrect. Seems to me that there is no need to EVER deal with the pseudokeys. (select house_id from houses where address = new.address) Select (select name_id from names where name = new.name), While its simple enough to write: SELECT where QID 'axo' and ANID 3 And check if the row exists then branch and either insert/update I can't help but look for a better way.
Insert or ignore into houses (address) select new.address where new.address is not null If the combination of QID and ANID already exists, that value should be updated, if the combination of QID and ANID doesn't already exist then it should be inserted. Insert or ignore into names (name) values (new.name) Select raise(ABORT, 'Name cannot be NULL') where new.name is null Where (peasants.name_id is null or peasants.name_id = names.name_id)Īnd (peasants.house_id is null or peasants.house_id = houses.house_id) Ĭreate trigger ins_person instead of insert into persons create table namesĪddress text not null collate nocase unique It is actually not needed for anything at all. It also does not really matter what some excrement-head thinks "after the fact" - they can either accept the answer "I don't know" (which by the way is an incorrect answer - the correct answer would be "that information was not recorded").Īnd going back to the post to which you replied, it only appears to the uneducated that there is a need to know the pseudokey for the row.
#SQLIGHT INSERT IF DOESNT ALREADY EXIST UPDATE#
It simply tries to add a record, and if that fails because of a constraint then it will try to update whatever record is causing the constraint to kick in.
Playing with pseudokeys will not be helpful in this regard. Okay, so SQLite doesn't use any column to select specific rows that it will try to update. Unless the inserted record contains a timestamp of when it was inserted, there is no way to tell when the record was inserted. Well, that is a design flaw (failure to store needed information) and has nothing whatsoever to do with the question asked.
0 kommentar(er)
