First off - is this a solution in search of a problem? Databases
are excellent at indexing and caching frequently used data. Though
your table has millions of rows and you are only really interested in
a few hundred you might find that performance is not noticeably any
different than if
Try do that whit phpmyadmin.
Regards,
Luis Morales
Bastien Koert wrote:
> if the archive tables structures are identical and no processing needs
> to be done, why not use a 'select into table where ' and use the ids
> of the records to choose the ones that move?
>
> Bastien
>
>> From: Jeffrey
At 22:28 19/05/2005 +, you wrote:
Message-Id: <[EMAIL PROTECTED]>
From: "John R. Sims, Jr." <[EMAIL PROTECTED]>
To: ,
Date: Thu, 19 May 2005 12:20:24 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="=_NextPart_000_0015_01C55C6D.22CC6B60"
Subject: More problems
> I'm trying to write a query that pulls details on a game record, as well
> as
> the officials assigned to the game (up to 4 officials may be assigned to
> each game, but that's not always the case).
>
> Game details are in the games table, and assignments are in the
> games_referees table (which
First, your design could be better. You are storing the same data
(referee) in multiple columns. More on that later.
I think the problem with your query is that you are using RIGHT OUTER
JOINS when you can and should be using LEFT JOINS. You want to make
sure you are always keeping the games re
> > SELECT g. * , concat( ref.fname, ' ', ref.lname ) AS ref, concat(
> > ar1.fname, ' ', ar1.lname ) AS ar1, concat( ar2.fname, ' ', ar2.lname
> )
> > AS ar2, concat( fourth.fname, ' ', fourth.lname ) AS fourth
> > FROM ( ( ( ( ( ( ( ( games g
> > RIGHT OUTER JOIN games_referees ref_ass O
I have a scenario where I have multiple inserts into a table and need to
know that ALL inserts were successful and if not that there were no
inserts.
I've seen an article on transactions in php/mysql and have a few
questions.
I have a table with orderID, itemIDs and itemQty
Someone with an order
