That would save some processing time right? If premature optimization is the root of all evil, I'm afraid you are halfway to hell. This is not a good reason t

That would save some processing time right? If premature optimization is the root of all evil, I'm afraid you are halfway to hell. This is not a good reason to make your app more complicated than it needs to be. For one thing, it isn't even easy to tell if your statement is true, let alone how true it is. (i.e. it may be true that you save a few milliseconds, but is that even going to be significant?) If there is a UI reason why you have to have the user specify 25 uploads on one HTML page and then do them all at once, that's one thing. (I'd use the big-pile-of-hidden-HTML-fields approach; that has the fewest moving parts, it's simple to conceptualize, and I don't think the other methods will make a big difference from the user's perspective.) But don't try to work around your DB until you absolutely have to. Use it. That's what it's there for.