set sql_mode='MYSQL323'; Query OK, 0 rows affected (0.00 sec) -----Original Message----- From: pgsql-general-owner@xxxxxxxxxxxxxx [mailto:pgsql-general-owner@xxxxxxxxxxxxxx]On Behalf Of Scott Marlowe Sent: Tuesday, October 25, 2005 3:24 PM To: Wes Williams Cc: 'Jan'; pgsql-general@xxxxxxxxxxxxxx Subject: Re: PostgreSQL vs mySQL, any performance difference for Cool. Does it still error out after issueing: set sql_mode='MYSQL323'; ??? Just wondering if bounds checking is still optional but is now op-out instead of opt-in, or if it's something that you can no longer turn off. The whole idea of correct behaviour being an option is pretty bad, but hopefully at least the defaults are for proper behaviour, or are heading that way. On Tue, 2005-10-25 at 13:52, Wes Williams wrote: > For what it may be worth, executing the same commands into MySQL > 5.0.15-nt-max (Win XP Pro) the following it received: > > mysql> create table test (i1 int); > Query OK, 0 rows affected (0.41 sec) > > mysql> insert into test values (123913284723498723423); > ERROR 1264 (22003): Out of range value adjusted for column (i1) at row 1 > > mysql> select * from test; > Empty set (0.03 sec) > > > Finally an improvement! > > ============================================================ > -----Original Message----- > mysql> create table test (i1 int); > Query OK, 0 rows affected (0.07 sec) > > mysql> insert into test values (123913284723498723423); > Query OK, 1 row affected, 2 warnings (0.07 sec) > > mysql> select * from test; > +------------+ > | i1 | > +------------+ > | 2147483647 | > +------------+ > 1 row in set (0.00 sec) > > And other fun things. > ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
