On Tue, 20 Jun 2006, Dirk Jagdmann wrote:
Column id should be indexed indeed. Anyway, I'm not sure about any
performance improvement using that last method, as the most consuming
operation might be the DELETE operation, not really the SELECT operation,
when dealing with a huge volume of data.
why worry, there are a maximum of 30 Entries in this table anyway. So
even the most unoptimized select and delete combinations should be
very fast...
Well, it's 30 entries per account and likely 1000s of accounts, but still that
would only be 30,000-90,000 entries, so shouldn't be too bad.
--
Jeff Frost, Owner <[EMAIL PROTECTED]>
Frost Consulting, LLC http://www.frostconsultingllc.com/
Phone: 650-780-7908 FAX: 650-649-1954
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
