On 8/24/05, Haines, Charles A. <HainesCA@stripped> wrote:
> To be honest, storing files in a database is a big debate. I wouldn't
> recommend storing the files in the database as it causes the database to
> become huge very quick. Rather another solution would be to store the files
> in a directory structure and store a file path in the database. This method
> keeps the database small, while maintaining the file structure.
>
yeah, I was thinking about that. I think I'll follow your suggestion.
> --chuck
>
> --
> Charles Haines
> Software Engineer / QA
> Remote Sensing Lab - Andrews
> ------------------------------
> Phone: (301) 817-3409
> Pager: (800) 759-8888 #1209278
> Email: hainesca@stripped
> ------------------------------
>
> This e-mail and any attachments may contain privacy act information. If you
> received this message in error or are not the intended recipient, you should
> destroy this message and any attachments, and you are prohibited from
> retaining, distributing, disclosing, or using any information contained
> herein. Please inform us of the erroneous delivery by return e-mail. Thank
> you for your cooperation.
> -----Original Message-----
> From: ZeeGeek [mailto:zeegeek@stripped]
> Sent: Tuesday, August 23, 2005 10:49 AM
> To: mysql++
> Subject: How to store files
>
> I'm not sure about how to store a file into the database. I know that the
> field type is blob and I have to open the file with fstream in binary mode.
> Do I use a char * to store the file into the memory and then put it in the
> database?
>
> --
> Dell Inspiron 600m
> Pentium-M 1.6G
> 512MB, 60G
> ATI 9000 Mobility
>
> --
> MySQL++ Mailing List
> For list archives: http://lists.mysql.com/plusplus
> To unsubscribe: http://lists.mysql.com/plusplus?unsub=1
>
>
>
> --
> MySQL++ Mailing List
> For list archives: http://lists.mysql.com/plusplus
> To unsubscribe: http://lists.mysql.com/plusplus?unsub=1
>
>
--
Dell Inspiron 600m
Pentium-M 1.6G
512MB, 60G
ATI 9000 Mobility
