Hi, I'm doing a select with some WHERE with AND and OR...
But it differs from server 6.5.3 to 9.7 in a great way....
because of my use of f1>f2_t2 I don't get consistent result... it will now NOT use the where before AND...
i.e.(byraa is the ID for companyID).
SELECT RecID, personnr, navn, postnr, adresse, poststed, kommune, land, trossamfunn, sivilstand, statsborgerskap, doeddato, kode, byraa, OpprettetAv, OpprettetAv->ID as brukerID
FROM avdoed WHERE byraa = '1' AND (navn LIKE '%Tjelta%' OR Poststed LIKE '%Tjelta%' OR land LIKE '%Tjelta%' OR Kode LIKE '%Tjelta%' OR Personnr LIKE '%Tjelta%' OR doeddato LIKE '%Tjelta%' OR kommune LIKE '%Tjelta%' OR adresse LIKE '%Tjelta%' OR pers_fester->navn LIKE '%Tjelta%' OR seremoni->Gravsted_sistGravlagt LIKE '%Tjelta%' )
ORDER BY Kode DESC
LIMIT 25
using the -> for name search I get result of both byraa 1 and byraa 2.... I should only have byraa 1, since that is the value of byraa in my search...
Doing the same in server 6.5.3, it works perfectly... but doing it in 9.7, it does not use the byraa value at all...
If I remove the -> parameters, then it works in 9.7.... so it is doing something wrong with the -> operator...
Broken ?