What most sites do is store in the DB a reference to the page (serial, ID, etc.) and the page itself in a file in a specific directory (a repository). This is one reason for URL's including many numbers and letters. This approach lends itself to storingn documents in a compressed format for instance. My feeling is that if you are storing raw documents sooner or later there will be one that is too large. Or there will be many of them if you choose to limit the size, so many infact, that it will be impractical to limit the size of all pages. I think you might as well kill the problem from the start than create a monster that will wake up one day and eat you and your clients. :-)
Cheers, Gerardo PS - Am I wrong or this is slightly off-topic? On Wed, 29 Sep 2004, Steffen Heil wrote: > Hi > > I need to store webpages in the database. > Until now I used BLOBs for this, but I think about switching to VARCHARs. > > It would not be a problem to limit the content to say 10000 CHARs. > However I am using ISO8859_1. (I think this is a one-byte-charset?) > > What would you recommend? > > Regards, > Steffen > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
