Benny Pedersen wrote on 4/01/23 3:19 am:
https://github.com/apache/spamassassin/blob/trunk/lib/Mail/SpamAssassin/SQLBasedAddrList.pm#L310 imho this line
I agree, but I don't see from looking at that line how the SQL query can have more than one table involved, and from the description of what "column reference is ambiguous" means I don't see how a query with one table in it can get a column reference is ambiguous error.
If you can't get the full dbg line, perhaps someone who actually uses SQL based awl might be able to jump in here, that's the limit of what I can figure out.
I was wrong when I said that... The dbg line does not include the full query anyway, just the arguments.
I don't know if the dbg line you get to is line 331 or 347, they both look the same. However, if you can edit those to also output $sql you can see the exact SQL query that is producing the error.
Someone who knows SQL better than I do could probably figure out from that how it could produce a column reference is ambiguous error. Or if you could add $sql to the dbg statements and post the full dbg output without that truncation, I could probably Google enough to figure it out.
I'm not set up to easily test with postgres AWL here, so it would help if you could generate the dbg lines with the additional info.
it worked in 3.4.6
If anyone else reading this is using 4.0.0 and postgres for AWL, are you seeing or not seeing this problem?
