On Thursday 13 July 2006 16:52, Peter Brawley wrote:
> Jean-Claude
>
> >I agree that LEFT JOIN is probably part of the solution. But the command
> > you suggest do not work, perhaps because several Chimeric_Cluster_IDs and
> > Unigene_ID are void or NULL. I want a list of AC from
> > Chimeric_Clus
Jean-Claude
>I agree that LEFT JOIN is probably part of the solution. But the command you
>suggest do not work, perhaps because several Chimeric_Cluster_IDs and
>Unigene_ID are void or NULL. I want a list of AC from Chimeric_Cluster_IDs
>that are not found in the gene_length table (Unigene_
On Thursday 13 July 2006 14:19, Peter Brawley wrote:
> Jean-Claude
>
> >But how to list all AC in Chimeric_Cluster_IDs _ABSENT_ from the
> > gene_length table, this one for instance :
> >mysql> select Chr_Name, Unigene_ID from gene_length where
> >Unigene_ID='Mm.371574';
> >Any idea ?
>
> That is c
Jean-Claude
But how to list all AC in Chimeric_Cluster_IDs _ABSENT_ from the gene_length
table, this one for instance :
mysql> select Chr_Name, Unigene_ID from gene_length where
Unigene_ID='Mm.371574';
Any idea ?
That is called an exclusion join. To get at it, you need to adopt
explicit joi
Hello all
I just suscribed to this list.
I am a scientist working in Strasbourg (France) on problems related to gene
expressions.
I have a first question : I am comparing 2 tables, "gene-length" and
"150genes".
mysql> describe 150genes;
+--+--+--+-+-
>From the manual:
6.3.2.2 Case-Sensitivity
BINARY
The BINARY operator casts the string following it to a binary string.
This is an easy way to force a column comparison to be case-sensitive
even if the column isn't defined as BINARY or BLOB:
mysql> SELECT "a" = "A";
-> 1
mysql> SELECT B
This msg keeps bouncing off the list.
First off, thanks for the hint on displaying several pages of news. :-)
Am having a bit of a weird problem with a SELECT on my MYSQL database:
If i use this:
SELECT * FROM tablehere WHERE userid = '$uid' AND password = '$pwd'
with $uid and $pwd bein
>Just when I thought I was getting the hang of this mysql stuff, the simplest
>of tasks
>is causing me to think about pulling my hair out.
>
>My table:
>
>NEWS {
> newsID (INT(3), AUTO-INCREMENT),
> newsTitle (VARCHAR (50)),
> newsText (BLOB),
> newsDate (DATE)
>}
It's
Very interesting addition to message...
Forgot to mention what the problem-query produces: Nothing.
Cheers,
Tom.
-Original Message-
From: Tom Norwood [mailto:[EMAIL PROTECTED]]
Sent: 27 July 2002 19:39
To: mysql-list
Subject: Date Comparison Problem...
Just when I thought I was
Just when I thought I was getting the hang of this mysql stuff, the simplest
of tasks
is causing me to think about pulling my hair out.
My table:
NEWS {
newsID (INT(3), AUTO-INCREMENT),
newsTitle (VARCHAR (50)),
newsText (BLOB),
newsDate (DATE)
}
I just want to filter
The example query comparing a datetime column against NOW() returns an empty
set of rows under 3.23.49. The same query against the same database returns
two rows under 3.23.48. In my opinion the 3.23.48 behaviour is correct and
3.23.49 appears to be incorrect. This happens under Linux 6.2 using t
At 11:01 PM -0600 1/20/01, Andrei Zmievski wrote:
>At 06:34 PM 1/20/01 -0800, Jeremy D. Zawodny wrote:
>>MySQL does trailing whitespace removal on all VARCHAR data as
>>described in the manual.
>
>Hmm, well that presents a problem in my application that counts on
>exact comparisons - I guess a wa
At 06:34 PM 1/20/01 -0800, Jeremy D. Zawodny wrote:
>MySQL does trailing whitespace removal on all VARCHAR data as
>described in the manual.
Hmm, well that presents a problem in my application that counts on exact
comparisons - I guess a way to do it is to use 'like' instead of '='?
-Andrei
On Sat, Jan 20, 2001 at 02:46:49PM -0600, Andrei Zmievski wrote:
> I recently ran into a problem when doing comparison against varchar
> field. Basically, comparing 'foo' and 'foo ' (note extra space)
> against the records produced the same results - almost as if MySQL
> trims the whitespace from
Hi,
I recently ran into a problem when doing comparison against varchar
field. Basically, comparing 'foo' and 'foo ' (note extra space) against
the records produced the same results - almost as if MySQL trims the
whitespace from the search parameter before running the search. Can
anyone shed ligh
15 matches
Mail list logo
