You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Avoid misbehavior in foreign key checks when casting to a datatype for which
the parser supplies a default typmod that can result in data loss (ie,truncation). Currently that appears to be only CHARACTER and BIT.We can avoid the problem by specifying the type's internal name insteadof using SQL-spec syntax. Since the queries generated here are only usedinternally, there's no need to worry about portability. This problem isnew in 8.3; before we just let the parser do whatever it wanted to resolvethe operator, but 8.3 is trying to be sure that the semantics of FK checksare consistent. Per report from Harald Fuchs.