er chunk. I am
trying to design it well enough though that we could in the future use
all of the Landsat imagery for the entire U.S. (also 6km x 6km chunks
at 30m resolution). There are about 90 different possible statistics
per landscape.
Thx,
Seth
On Sunday, March 2, 2003, at 06:31 PM, Bruce Feist
) SELECT AVG(column1), FROM table1 LEFT
JOIN temp ON temp.xy=table1.xy WHERE AND
temp.xy IS NOT NULL; (maximum of 20k rows, less after both WHERE
statements tho)
Does this sound like the best way to accomplish this? Any suggestions?
Thx,
Seth
On Sunday, March 2, 2003, at 03:41 PM, Seth Price
Hi list, I am sure that there is an efficient way to do this in SQL, I
just can't figure out what it is.
I am dealing with two tables. One, I'll call table1 has about 90
columns and 20k rows, each number in column "xy" is unique. The other
has about 90 columns and about 200k rows, and there wil
nough for now, but in the future I may have
approx. 3,500k rows, so I am a little more worried about my SELECT
performance then.
~Seth
On Tuesday, February 11, 2003, at 12:54 PM, Peter Grigor wrote:
- Original Message -
From: "Seth Price" <[EMAIL PROTECTED]>
To: <
Has the maximum number of keys in a MyISAM table been tested more since
this post? Is it possible to get above 64 keys? (I'm going for 90, btw)
~Seth
to get past spam filter: MySQL sql query
Subject: Re: Maximum of 16 indexes per table
From: Michael Widenius
Date: Fri, 30 Jul 1999 23:57:19 +0300
