On Thu, 31 Jul 2008 13:57:07 -0400, Perrin Harkins [EMAIL PROTECTED]
wrote:
On Thu, Jul 31, 2008 at 12:59 PM, Chris W [EMAIL PROTECTED] wrote:
So my question is, is doing that way better than making the query more
complex with all the joins?
If by better you mean faster then yes, it
On Fri, Aug 1, 2008 at 7:32 AM, Rudolf Lippan [EMAIL PROTECTED] wrote:
How would you get duplicated data? In one case you have an integer
and in the other you have the value, but you still have to store one token
of information with the row.
I meant in the case of storing the value
This is really a MySQL and php question since one of the two options
require programming. Of course I don't think the result would be
different in a different programming language.
I use lookup tables a lot. I have had between 5 to 10 lookup tables for
one table of data. Normally
On Thu, Jul 31, 2008 at 12:59 PM, Chris W [EMAIL PROTECTED] wrote:
So my question is, is doing that way better than making the query more
complex with all the joins?
If by better you mean faster then yes, it probably is marginally
faster. It would be simpler to just use the actual values you
]
Fax to:
05/18/2004 08:51 Subject: lookup tables, populating
automatically
I asked a question earlier about how to handle lookup tables, I think this
is a little more clear as to what I was trying to ask.
if I want to relate a contact to an organization, I know I can create a
table that contains contact_ids and org_ids.
But, how do I enter that information gracefully
On Wed, Feb 27, 2002 at 09:14:51PM -0800, Jeff Kilbride wrote:
Is there a rule of thumb for small tables and whether they should be
indexed? I have several small, two column lookup tables with few
rows (100-300) and some very small tables ( 10 rows). I don't plan
on indexing the very small
Actually, I've been looking pretty closely at a couple of other tables I
wanted to implement as HEAP tables -- and I didn't even think about moving
my little lookup tables into HEAP. :)
Thanks!
--jeff
- Original Message -
From: Jeremy Zawodny [EMAIL PROTECTED]
To: Jeff Kilbride [EMAIL
wrote:
JK Is there a rule of thumb for small tables and whether they should be
JK indexed? I have several small, two column lookup tables with few rows
JK (100-300) and some very small tables ( 10 rows). I don't plan on
JK indexing
JK the very small ones, but what about the others?
It depends
Hi Egor,
Thanks for the reply. Does it actually hurt to index them on lower volumes
of traffic? Or is it neglible?
--jeff
- Original Message -
From: Egor Egorov [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, February 28, 2002 8:40 AM
Subject: Lookup tables and indexing
Jeff
Is there a rule of thumb for small tables and whether they should be
indexed? I have several small, two column lookup tables with few rows
(100-300) and some very small tables ( 10 rows). I don't plan on indexing
the very small ones, but what about the others?
Thanks,
--jeff
sql,query
11 matches
Mail list logo
