At 05:32 AM 18/07/2009, you wrote:

>Hello, I need to store some images in my FB2.1 database. I have a domain:
>
>CREATE DOMAIN IMAGEN AS
>BLOB SUB_TYPE 0 SEGMENT SIZE 100;
>
>My question is; Is here any practical problem in storing, let's say, 3Mb images
>in blob fields in the database?

Of course, the database *can* store 3MB images, but why overload your administration task (think of backups!) by storing objects that won't change? Consider also the extra overhead in the cache and across the network in possibly retrieving large blobs that your users normally would need to have at the client only on request, e.g. via a Show/Select image button.

>I ask this because I'm thinking in creating a
>special folder inside my app folder, put the images there and in the datase just
>save the path to the images. Does it make sense?

Yes. You can include the files in your periodic filesystem backup regime, preferably performed at some time when the database users don't need access.

>The images will be attached to production orders, therefore the table containing
>the images will grow with time. It can receive more than 50 orders a day with 3
>or 4 images each. Probably this is not too much for a database!!

Well, it gets down to a question "How much is too much?" Consider how the images will be used, how much backup time you can spare for reading these large objects into a backup file, etc. Only you can know these parameters...and one supposes that you will want to test both options with real data and traffic loads to figure out what each option would cost in terms of time and resource.

./heLen