From: | Don Baccus <dhogaza(at)pacifier(dot)com> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: MySQL search query is not executing in Postgres DB |
Date: | 2012-02-18 00:19:48 |
Message-ID: | 80D838BF-9DA4-4A28-B115-DAEC3E3FBF4A@pacifier.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Feb 17, 2012, at 4:12 PM, Josh Berkus wrote:
> On 2/17/12 12:04 PM, Robert Haas wrote:
>> The argument isn't about whether the user made the right design
>> choices; it's about whether he should be forced to insert an explicit
>> type cast to get the query to do what it is unambiguously intended to
>> do.
>
> I don't find INTEGER LIKE '1%' to be unambiguous.
>
> Prior to this discussion, if I had run across such a piece of code, I
> couldn't have told you what it would do in MySQL without testing.
If someone showed it to me without mention MySQL I'd say:
"oh, it's an error".
>
> What *does* it do in MySQL?
And knowing it's MySQL … "oh, probably *not* an error", but like you … I'd be mystified.
Should 01 like '0%' match?
----
Don Baccus
http://donb.photo.net
http://birdnotes.net
http://openacs.org
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-02-18 02:17:27 | Re: Notes about fixing regexes and UTF-8 (yet again) |
Previous Message | Josh Berkus | 2012-02-18 00:12:37 | Re: MySQL search query is not executing in Postgres DB |