From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
---|---|
To: | Marti Raudsepp <marti(at)juffo(dot)org> |
Cc: | pgsql-general(at)postgresql(dot)org, premanand <kottiprem(at)gmail(dot)com> |
Subject: | Re: MySQL search query is not executing in Postgres DB |
Date: | 2012-02-17 21:15:46 |
Message-ID: | 4F3EC382.2020101@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 02/17/2012 08:01 AM, Marti Raudsepp wrote:
> On Fri, Feb 17, 2012 at 17:13, Adrian Klaver<adrian(dot)klaver(at)gmail(dot)com> wrote:
>> Why not use:
>> " SELECT * FROM<Table-name> WHERE CAST(Table.ID as TEXT) LIKE '1%' "
>>
>> as the MySQL query also? MySQL supports the CAST function.
>
> Nope, trying to use CAST() in an interoperable manner is a lost cause.
> Sadly MySQL and PostgreSQL don't agree over the cast types. MySQL's
> CAST doesn't recognize varchar or text. Both support CHAR, but they
> work differently (MySQL's char behaves like PostgreSQL's varchar):
>
Well I guess the choices are put back the implicit cast or change the
data type of the Table.ID column in Postgres to varchar.
>
>
> Regards,
> Marti
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-02-17 21:21:44 | Re: Pokey Fedora Updates for Postgresql? |
Previous Message | Andy Colson | 2012-02-17 20:58:58 | Re: select as params to function |