I have a table with numerous columns but needing to perform a query
based on three columns:
Lab_number, result, release_time.
What I want to do is search for lab_number where there is a result but
not released. The problem that is making this difficult for me, is that
there are multiple entries
On Wed, 2007-01-17 at 09:56 -0600, Peter Brawley wrote:
Daniel,
find the lab_number where ALL the tests have been performed and
not the lab_numbers which have partial results.
SELECT t1.lab,t1.res,t1.dt
FROM tbl t1
WHERE NOT EXISTS(
SELECT lab FROM tbl t2 WHERE t1.lab=t2.lab AND
On Wed, 2007-01-17 at 11:47 -0600, Peter Brawley wrote:
Daniel,
CREATE TABLE tbl (
lab_number int(11) default NULL,
result int(11) default NULL,
release_time datetime default NULL
);
select * from tbl;
+++-+
| lab_number | result |
Assuming a decent spec server, would a simple search query on a big
indexed table be quicker than searching the amount of data divided into
separate tables?
The kind of situation I have in mind is a database of events during a
year, this table could top 1,000,000 enteries on the vague kind of
At 10:55 AM + 3/29/02, DL Neil wrote:
Scenario:
- two tables, one for photos, and one for collections
- zero or more photos can belong to a collection
- the database may not know the collection_id requested
(i.e. the user on the browser side did something to request
a
I am considering the intensive 1 week MySQL class coming up
in SF. Has anyone here been through one of their
classes? How did it go?
The web site doesn't list a location, and
they don't answer the phone (strikes 1 2...)
Off-list responses are fine. I'd just like to know
that someone found
At 10:55 AM + 3/29/02, DL Neil wrote:
We can hit:
a) no collection
b) a collection that hasn't had any photos moved/uploaded to it yet,
or..
c) a collection with one or more photos (the normal, everything's
fine case)
Let us know how you get on!
Thanks again DL, my first stab at using
I have a question about determining which case
occurred when there are no matches - using two tables.
Scenario:
- two tables, one for photos, and one for collections
- zero or more photos can belong to a collection
- the database may not know the collection_id requested
(i.e. the user on
