Re: Query Confusion!

There are only 500 records in total of which three are relevant to the 'plus' query. But there is only 1 relevant result from the 'real' query, and that did return a result. Brent Baisley wrote: Is the plus query return more then 50% of the records? If so, MySQL won't return anything since

Re: Query Confusion!

Is the plus query return more then 50% of the records? If so, MySQL won't return anything since the result set isn't that relevant. Brent Baisley Systems Architect On Apr 11, 2008, at 8:08 AM, Barry wrote: I am confused ( nothing new there), what I thought was a simple search is proving no

Query Confusion!

I am confused ( nothing new there), what I thought was a simple search is proving not to be so, Can anyone tell me why this query for the word 'plus': mysql> SELECT * -> FROM booktitles -> WHERE MATCH (category , publisher , bookTitle , author) -> AGAINST (CONVERT( _utf8'plus'USING latin1 ) -> I

Re: update query confusion

Nick, Friday, June 14, 2002, 3:40:23 PM, you wrote: NW> I can't work out why this query is also updating a TIMESTAMP col? It's a paticular feature of TIMESTAMP column. Read the manual: http://www.mysql.com/doc/D/A/DATETIME.html NW> UPDATE news SET title = 'new title', text = 'new text' WHE

Re: update query confusion

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 * and then Jay Blanchard declared > other column changes value. (Note that an UPDATE that sets a column to the > value it already has will not cause the TIMESTAMP column to be updated, > because if you set a column to its current value, MySQL ign

RE: update query confusion

{snip] I can't work out why this query is also updating a TIMESTAMP col? UPDATE news SET title = 'new title', text = 'new text' WHERE id = '4' [/snip] Because, according to TFM; (http://www.mysql.com/doc/D/A/DATETIME.html) Automatic updating of the first TIMESTAMP column occurs under any of the

update query confusion

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all I can't work out why this query is also updating a TIMESTAMP col? UPDATE news SET title = 'new title', text = 'new text' WHERE id = '4' The table is very simple: * id INT * date TIMESTAMP // this is current date when 'updating'? * ti

Re: 24 hour query confusion....

AIL PROTECTED]> To: "Andy" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: 20 November 2001 15:47 Subject: Re: 24 hour query confusion > 3076 is 2:53 in the morning, not the afternoon. > > On Tuesday 20 November 2001 08:46 am, Andy wrote: > > Summary > &g

Re: 24 hour query confusion....

3076 is 2:53 in the morning, not the afternoon. On Tuesday 20 November 2001 08:46 am, Andy wrote: > Summary > If I have a filed of type "DATETIME" in a table and do a query with an > order on that field than records with a datetime in the afternoon are > returned before articles in the morning. >

24 hour query confusion....

Summary If I have a filed of type "DATETIME" in a table and do a query with an order on that field than records with a datetime in the afternoon are returned before articles in the morning. EG: mysql> select pubtime,articleid,headline from articles where articleid mysql> >3050 order by pubtime;