Andreas Pflug wrote: > Peter Eisentraut wrote: > > >I was just annoyed to find out that a foreign key doesn't check whether > >the referenced column has a sufficiently similar data type, it only checks > >whether an = operator exists. This masks schema design errors and typos. > >Should this be tightened up, for example using the castability > >characteristics between the two data types? > > > > > > Sounds like a good idea. IMHO normally only *equal* data types should be > referenced in a good data model design, but there's probably the need > for some relaxed check option too.
Yes, we already talked about throwing a warning if the primary/foreign key data types are mismatched. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend