-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Billy Holmes wrote: >> It would >> also require many more queries to execute > > That's a ~62% savings. You can use a medium INT to reference the > pathname, and then use inner joins in your queries.
You should set up a sf.net project and then we could move discussion off this list... :) I think that splitting the path may be a good idea. Inner joins really do not add much of a penalty to your query as long as everything is indexed. However, I'm not convinced it makes a big difference. So, the DB is 100MB - it isn't like you're sending that over a wire at all - you just need to store it on the DB server. Having 2 20MB tables instead of 1 100MB table isn't going to make a big difference in final performance. The main area to optimize size-wise is what gets sent over the wire - and that is just a list of packages/flags already indexed so that clients do not do needless work. That will be pretty small in any case. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDYPkgg2bN8aFizRkRAhKtAJ0fiWZy6/GS0uaewIm9FgE/di/yxQCfYx1l e/wKtM59CdWtxvTx+3H/rcY= =hwBL -----END PGP SIGNATURE-----
smime.p7s
Description: S/MIME Cryptographic Signature
