Naz,
That query logic runs without a error on the server I have to hand
(5.0.37), but it has three issues:
(i) unless there is an exceptionless 1:1 relationship between
group_post_mod_option.option_id and group_post_mod_option.option_name,
results for the latter column will be meaningless be
, October 19, 2006 11:47 PM
To: Don O'Neil
Cc: mysql@lists.mysql.com
Subject: Re: Problem with query on 5.11
Don O'Neil wrote:
> Why does this query return no results:
>
> SELECT * FROM FileList WHERE MATCH Filename AGAINST ("9640")
>
> When there are entries in the F
Yes, there is a full text index, there are about 12,000 rows or so.
Don
-Original Message-
From: Chris [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 19, 2006 11:47 PM
To: Don O'Neil
Cc: mysql@lists.mysql.com
Subject: Re: Problem with query on 5.11
Don O'Neil wrote:
Jerry,
Is "9640" a word by itself? A full-text search wouldn't find "abc9640",
No a full text search would find numbers pretending to be a "word", the
full text search has a fairly high level definition of a "word". Try
searching for "1960" over at http://ftvdb.bfi.org.uk/search.php.
Regar
Jerry,
Is "9640" a word by itself? A full-text search wouldn't find "abc9640",
No a full text search would find numbers pretending to be a "word", the
full text search has a fairly high level definition of a "word". Try
searching for "1960" over at http://ftvdb.bfi.org.uk/search.php.
Regar
Is "9640" a word by itself? A full-text search wouldn't find "abc9640",
you'd need to use LIKE for that.
Regards,
Jerry Schwartz
Global Information Incorporated
195 Farmington Ave.
Farmington, CT 06032
860.674.8796 / FAX: 860.674.8341
> -Original Message-
> From: Don O'Neil [mailto:[EM
Don O'Neil wrote:
Why does this query return no results:
SELECT * FROM FileList WHERE MATCH Filename AGAINST ("9640")
When there are entries in the Filename list that have 9640 in them?
How many rows are in the table? Full text won't work with only a couple
of rows.
And you do have a full
From: "Jon Miller" <[EMAIL PROTECTED]>
To:
Subject: Problem with query
Date: Tue, 24 May 2005 19:40:32 +0800
Quite new to MySQl and queries in general and would like some help in the
following query:
select prDate, prName, prLEmployee, prDescription, prTotalHours, prLStatus,
prCompletionDate,
Hello.
Looks like passwords in your table are stored in old short format.
Use old_password() instead of password(). See:
http://dev.mysql.com/doc/mysql/en/password-hashing.html
Lancer Emotion 16 <[EMAIL PROTECTED]> wrote:
> Hello everbody,i have a problem with mysql and i wish you could
Lancer Emotion 16 wrote:
I have this table named users :
+
| ID | user | pass | thegroup | firstname | surname | enabled
+++--+--+---+-+-
| 1 | Admin | *4ACFE3202A5FF5CF467 | 1 | Mr| Admin | 1
The pas
Luiz Rafael Culik Guimaraes wrote:
Dear Friends
Running the follow query
select max( sr_recno) from test_table down work for re
the error id returned by mysql_errno is 3731792
server is 4.1.1a-alpha
Table structure is
SR_DELETEC char(1)
SR_RECNO bigint(15) PRI auto_increment
VALUE double(18,6)
On Tue, 2003-11-11 at 00:15, Alaios wrote:
> what a front-end is? And what OO1.1.0 provides?
MySQL is a database server and a front-end is another program that you
use to get to that server and use the database. OpenOffice is a complete
office software package (word processor, spreadsheet, ...) th
what a front-end is? And what OO1.1.0 provides?
Marc <[EMAIL PROTECTED]> wrote:I'm using OpenOffice 1.1.0 as a front-end to MySQL
4.0.14 on Gentoo
Linux and can't compare a field to CURDATE(). The error is, "The field
cannot be compared with a date". The column is formatted as a DATE, and
I can p
Leonardo Javier Bel? wrote:
>Hi ALL!
>I have a problem with this query, because it keeps failing and I dont
>know why (it says that the concat statement is wrong but there is nothing on
>the online docs...)
>
>select st.id, concat(st.required), st.name from states st, agenda ag left
>outer j
You have it right. But if the user searches for new power boats, and
doesn't specify a make, make should not appear in your WHERE clause. The
query has to be different depending on the criteria that have been
chosen (or not chosen, as the case may be). Prior to executing the
query, look at all
Bill Lovett wrote:
Hello,
You're getting all new boats + all sail boats + all boats of type x
because you're using ORs. If you only want records that match all the
criteria, use ANDs instead.
If I use AND, wouldn't all conditions need to be true to return a
result? In the case of the sear
Hello,
You're getting all new boats + all sail boats + all boats of type x
because you're using ORs. If you only want records that match all the
criteria, use ANDs instead.
SELECT * FROM boat WHERE condition='$condition' AND type='$type'
Or you might try
SELECT * FROM boat WHERE (condition='n
Since it can't use an index, and has to sort the output, what
exactly is unexpected?
Norris, Joseph wrote:
>Group,
>
>I have the following query:
>
>select phones.*, ops.plid, ops.box, ops.mac
>from phones, ops where
>(ops.box = 'Mcds') or (ops.box = 'Mn3300') and
>(phones.suffix1 = ops.phone
Depends on how the fee paymnents are defined. At its simplest:
SELECT Members..Name FROM Members WHERE NOT(Members.MemberID =
FEE_PAYMENTS.MenmbersID)
would select members that have no fee payment records. You could build
on it from there...
For the mySQL gurus, sorry about the syntax guys, I
select * from MEMBERS,FEE_PAYMENTS where FEE_PAYMENTS.PAID = '0' and MEMBERS. MemberID
= FEE_PAYMENTS. MemberID;
assuming you have a field PAID, with values 0 or 1,or even YES or NO
cheers
Mark
>I am having a small problem with a small mysql query...
>
>I want to make a list of:
>"WHO HAS NO
At 10:36 -0300 2/1/02, [EMAIL PROTECTED] wrote:
>Hi,
>
> I Have a problem with transaction controls... runing the query
>"begin; select * from table; commit;", this query run perfectly in the
>shell, but in my code return error of sintax.
If you're using some kind of MySQL API within a prog
What kind of code ?
I typically send each of those in as separate queries.
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, February 01, 2002 8:36 AM
Subject: Problem with query
> Hi,
>
> I Have a problem with transaction controls... runing the query
I don't see any code or errors.
[EMAIL PROTECTED] wrote:
>Hi,
>
> I Have a problem with transaction controls... runing the query
>"begin; select * from table; commit;", this query run perfectly in the
>shell, but in my code return error of sintax.
>
> Somebody help me?
>
>
>--
=NULL" gives the same
results as " WHERE xx IS NULL".
Or would that be an unusual thing to request.
Andrew Murphy
-Original Message-
From: jim barchuk [mailto:[EMAIL PROTECTED]]
Sent: 27 October 2001 8:32 pm
To: Paul DuBois
Cc: [EMAIL PROTECTED]
Subject: Re: Problem with quer
Hi Paul!
On Sat, 27 Oct 2001, Paul DuBois wrote:
> At 9:38 -0400 10/27/01, jim barchuk wrote:
> >Hi Carl!
> >
> >> Paul DuBois writes:
> >>
> >> > NULL basically means "unknown value", so saying WHERE x = NULL cannot
> >> > work, even if x is NULL. That means "where one unknown value = anoth
At 9:38 -0400 10/27/01, jim barchuk wrote:
>Hi Carl!
>
>> Paul DuBois writes:
>>
>> > NULL basically means "unknown value", so saying WHERE x = NULL cannot
>> > work, even if x is NULL. That means "where one unknown value = another
>> > unknown value", which cannot be evaluated with any certa
Hi Carl!
> Paul DuBois writes:
>
> > NULL basically means "unknown value", so saying WHERE x = NULL cannot
> > work, even if x is NULL. That means "where one unknown value = another
> > unknown value", which cannot be evaluated with any certainty. :-)
>
> It is sort of odd, though, that x = NULL
Paul DuBois writes:
> NULL basically means "unknown value", so saying WHERE x = NULL cannot
> work, even if x is NULL. That means "where one unknown value = another
> unknown value", which cannot be evaluated with any certainty. :-)
It is sort of odd, though, that x = NULL returns something wh
At 15:54 -0600 10/26/01, Brendin wrote:
>Yours is the first and the winner! :) Thanks using is null worked in
>the query... Do you know why = doesn't work?
NULL basically means "unknown value", so saying WHERE x = NULL cannot
work, even if x is NULL. That means "where one unknown value = anothe
Yours is the first and the winner! :) Thanks using is null worked in
the query... Do you know why = doesn't work?
-Original Message-
From: Ravi Raman [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 26, 2001 4:00 PM
To: Mysql; Brendin
Subject: RE: Problem with query
hi.
first of
hi.
first of many replies, i'm sure:
mysql> select count(compid) from dbLastFaxed where lastFaxedDateTime IS null
;
when you're looking for NULL fields, select where something IS NULL, instead
of '='
-Original Message-
From: Brendin [mailto:[EMAIL PROTECTED]]
Sent: October 26, 2001 5:46
31 matches
Mail list logo
