Gossamer Forum
Home : Products : Gossamer Links : Discussions :

Multiple Paths/Images HASHED or SIMPLE?

Quote Reply
Multiple Paths/Images HASHED or SIMPLE?
LinksSQL 2.05

1) If I have two images being uploaded (image_1 & image_2), should I have them store their images in different directories, or does it matter?

2) What does it mean to HASH a file? Why would or wouldn't I want it to
be HASHED?



Quote Reply
Re: [Evoir] Multiple Paths/Images HASHED or SIMPLE? In reply to
The hashed option allows greater efficiency with large databases.




PUGDOG� Enterprises, Inc.

The best way to contact me is to NOT use Email.
Please leave a PM here.
Quote Reply
Re: [pugdog] Multiple Paths/Images HASHED or SIMPLE? In reply to
Thanks Pugdog,

What sizes are we talking about?

Also, does it make sense to begin a project HASHED? I can't imagin our DB getting bigger than say, 1500 "links". But, is it better to just go ahead and have them be HASHED?

Also, about the file paths: Would it make more sense to have different directories for different image fields? Or does this not matter at all.

Last edited by:

Evoir: Sep 25, 2001, 10:10 AM
Quote Reply
Re: [Evoir] Multiple Paths/Images HASHED or SIMPLE? In reply to
Hi,

Hashed is useful if you are expecting more then 20,000 records. If you never come close, you can leave it as simple.

You should have different directories for different image fields, but it is not essential.

Cheers,

Alex
--
Gossamer Threads Inc.