Re: [HACKERS] Re: type coersion (was OR clause status)

> For example, the third number in the third line is 607, which is the
> amopopr, and is oideq. We know we can use this for the query because
> int4 and oid are identical, but the parser has already chosen the more
> appopriate 1137/oideqint4. If we could add an extra line to this file,
> perhaps:
>
> DATA(insert OID = 0 ( 403 427 607 3 btreesel btreenpage ));
>
> However, I don't think the access methods allow more than one line in
> this way.

I just tried adding the extra line, and initdb failed. I wonder if we
remove the oideqint4, if the parser will go for oideq?

--
Bruce Momjian | 830 Blythe Avenue
maillist(at)candle(dot)pha(dot)pa(dot)us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)