• Tom Lane's avatar
    Represent type-specific length coercion functions as pg_cast entries, · d70a42e6
    Tom Lane authored
    eliminating the former hard-wired convention about their names.  Allow
    pg_cast entries to represent both type coercion and length coercion in
    a single step --- this is represented by a function that takes an
    extra typmod argument, just like a length coercion function.  This
    nicely merges the type and length coercion mechanisms into something
    at least a little cleaner than we had before.  Make use of the single-
    coercion-step behavior to fix integer-to-bit coercion so that coercing
    to bit(n) yields the rightmost n bits of the integer instead of the
    leftmost n bits.  This should fix recurrent complaints about the odd
    behavior of this coercion.  Clean up the documentation of the bit string
    functions, and try to put it where people might actually find it.
    Also, get rid of the unreliable heuristics in ruleutils.c about whether
    to display nested coercion steps; instead require parse_coerce.c to
    label them properly in the first place.
    d70a42e6
preptlist.c 8.43 KB