Re: WL#946 and Changing time literal format

* Michael Widenius [09/02/03 19:24]: > Konstantin> Monty, I disagree with this statement. Our current users use the > Konstantin> current versions of the server. It's a separate question of what > Konstantin> support we're willing to give them and for how long. > Konstantin> In the new versions w

2nd call for papers: PostgreSQL Conference East

PostgreSQL Conference East is being held at historic Drexel University on April 3rd through 5th 2009 . This is the second call for papers. The call for papers ends Feb 23rd and speakers will be notified on the 27th. You may submit your talk here: http://www.postgresqlconference.org . We are looking

Re: WHERE vs. ON

2009/2/4 Baron Schwartz > On Tue, Feb 3, 2009 at 12:24 PM, Jerry Schwartz > wrote: > > Somebody, I think it was somebody from MySQL, said that you should never > put > > anything into a WHERE clause that could be put into the ON clause of a > JOIN. > > My guess is that this helps with the optimi

Re: WHERE vs. ON

Never tried it in MySQL and Im not in a position to do so at the moment but in Oracle you can do a left outer join in the where clause something like this SELECT t1.col1, t2.col2 FROM table1 t1, table2 t2 WHERE t1.join_col_name = t2.join_col_name(+) Does this not work in MySQL? Luckily, it

Re: like isn't behave as expected

>From http://dev.mysql.com/doc/refman/5.0/en/string-comparison-functions.html#oper ator_like: Note Because MySQL uses C escape syntax in strings (for example, ³\n² to represent a newline character), you must double any ³\² that you use in LIKE strings. For example, to search for ³\n², specify it

RE: like isn't behave as expected

>-Original Message- >From: Yariv Omer [mailto:yar...@jungo.com] >Sent: Wednesday, February 04, 2009 10:50 AM >To: mysql@lists.mysql.com >Subject: like isn't behave as expected > >Hi > >i have one row in the cpe_id column of the cpe_users table in my >database with the value: "d\d". > >when

RE: WHERE vs. ON

>-Original Message- >From: John Daisley [mailto:john.dais...@mypostoffice.co.uk] >Sent: Wednesday, February 04, 2009 10:41 AM >To: mysql@lists.mysql.com >Cc: Jerry Schwartz >Subject: Re: WHERE vs. ON > >Never tried it in MySQL and Im not >in a position to do so >at the moment >but in Orac

like isn't behave as expected

Hi i have one row in the cpe_id column of the cpe_users table in my database with the value: "d\d". when i am doing:select cpe_id from cpe_users where cpe_id = 'd\\d' >> I got the one result. when i am doing:select cpe_id from cpe_users where cpe_id like 'd\\d' >> I don't get any result! wh

Re: WHERE vs. ON

Never tried it in MySQL and Im not in a position to do so at the moment but in Oracle you can do a left outer join in the where clause something like this SELECT t1.col1, t2.col2 FROM table1 t1, table2 t2 WHERE t1.join_col_name = t2.join_col_name(+) Does this not work in MySQL? Never tried it be

RE: WHERE vs. ON

>-Original Message- >From: baron.schwa...@gmail.com [mailto:baron.schwa...@gmail.com] On >Behalf Of Baron Schwartz >Sent: Wednesday, February 04, 2009 10:03 AM >To: Jerry Schwartz >Cc: mysql@lists.mysql.com >Subject: Re: WHERE vs. ON > >On Tue, Feb 3, 2009 at 12:24 PM, Jerry Schwartz > wrot

Re: WHERE vs. ON

On Tue, Feb 3, 2009 at 12:24 PM, Jerry Schwartz wrote: > Somebody, I think it was somebody from MySQL, said that you should never put > anything into a WHERE clause that could be put into the ON clause of a JOIN. > My guess is that this helps with the optimization, but it seems > counter-intuitive