RE: Re: dealing with attachments (again)

[BBQ]

I second that. You would be increasing your performance by a great deal just by finding a clever way to keep the attachments directly on the filesystem. I would suppose that you have a user primary key and a message primary key, correct? If so, you could try doing a directory tree like:

/users/
      /user1/
            /attachmenta
            /attachmentb
            /attachmentc
      /user2/
            /attachmenta
            /attachmentb
            /attachmentc

Where userx would be the user pk and attachmentx would be the attachment pk (doh!). On the downside, it would probably be nice to develop a tool or cron job to keep track of lost attachments, old stuff and so forth...

#!/home/bbq/bin/perl
# Trust no1!

[Punto]

Well, my main concerns were:

- I need to be able to figure out the ammount of disk space that a user is using, in a fast and easy way.
- There is a security problem with saving the attachments on a public_html directory.
- (this is the most important) I'd like to have all the database in one place.

So there is no way to send the content of a _big_ file to mysql without using a lot of ram?

Thanks!