| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Coby Beck <coby(at)vec(dot)com(dot)au> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: implicit type conversions |
| Date: | 2003-06-05 18:58:57 |
| Message-ID: | Pine.LNX.4.44.0306051852290.2050-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Coby Beck writes:
> For example, many functions declared on (INTEGER) need to be changed to
> (BIGINT), type (TEXT) is no longer good enough when it is actually an
> integer being passed, things like this.
>
> Is there some kind of global setting or configuration I can modify rather
> than patching things all over the place? I have mixed feelings on these
> kinds of behind the scenes "favours" but for now I would just like it to
> work...
If you're desperate, you can read up on the system table pg_cast and
modify the column castcontext for the appropriate casting pairs.
--
Peter Eisentraut peter_e(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sean Chittenden | 2003-06-05 19:15:56 | Re: Anonymous CVS access |
| Previous Message | Andrew Sullivan | 2003-06-05 18:14:14 | Re: implicit type conversions |