On 7/29/16 3:13 PM, David Fetter wrote:
> I expect this kind of blather from MySQL, but you've brought up
> something that's been bothering me for awhile. PostgreSQL's response
> should look more like this:
>
> ERROR: month field value out of range: "2016-99-99"
> LINE 1: select
On Fri, Jul 29, 2016 at 09:20:12PM +0300, Nikolay Samokhvalov wrote:
> On Fri, Jul 29, 2016 at 5:28 PM, Jim Nasby wrote:
> >
> > The way I sum up MySQL vs PG for people that ask is to recount how they
> > "fixed" the Feb. 31st bug when they released strict mode
On Fri, Jul 29, 2016 at 5:28 PM, Jim Nasby wrote:
>
> The way I sum up MySQL vs PG for people that ask is to recount how they
> "fixed" the Feb. 31st bug when they released strict mode (something that
> they actually called out in the release PR). With strict mode
On 7/29/16 8:17 AM, Kevin Grittner wrote:
On Thu, Jul 28, 2016 at 8:39 PM, Tatsuo Ishii wrote:
> BTW, is there any opposite information, i.e. showing the
> limitation of MySQL comparing with PostgreSQL?
I'm not aware of a general list on the topic, but in reviewing
On Thu, Jul 28, 2016 at 8:39 PM, Tatsuo Ishii wrote:
> BTW, is there any opposite information, i.e. showing the
> limitation of MySQL comparing with PostgreSQL?
I'm not aware of a general list on the topic, but in reviewing
academic papers regarding transaction isolation I
On Fri, Jul 29, 2016 at 4:39 AM, Tatsuo Ishii wrote:
>
> Great translation.
>
> BTW, is there any opposite information, i.e. showing the limitation of
> MySQL comparing with PostgreSQL? I'm not familiar with MySQL, but
> occasionally hearing surprising (as a PostgreSQL user)
> Following Uber's case discussion, I found this talk by Alexey Kopytov to be
> really interesting:
> http://kaamos.me/talks/pgday16/strongmysql/strongmysql.html (online html,
> in Russian)
>
> I translated it to English:
>
>