Images stored in DB?

dirk wrote: Maybe that's a better way.
In your template you can insert the image in this way:

<img src="{joodb field|YOURIMAGEFIELD}" style="max-width: 320px; max-height: 280px;" alt="*">

I'll bear that in mind if I hit the file limit mentioned in my other post. For now we've uploaded about 15K image files, so I'll stick with that.

The pro version will have the opportunity to attach multiple images and files to your data soon.

I'm really impressed with joodb, to the point that I'm annoyed that I didn't see it sooner. We've been stuffing around with all manner of extensions, only to hit a brick-wall every time. I was just about to start writing a component when I saw joodb. I had my framework up and running with it in a couple of hours.

So, it goes without saying my group will take a subscription.

BTW, our work in progress is here - it's still a bit rough, but I'm confident it will shape up over the next week.

Cheers and thanks again.

GuiGuy wrote: I've got an uneasy feeling that our host is still on EXT3 and the limit applies.

I never heard about such a limit. If you provider limits the number of files you should change the provider. Sometimes the FTP-Servers display only the first XXXX files.
Then you can use php filemagers like explorer.

If your images are not too big you can also use a blob-files to store your images. Be aware that you might get problems if you want to import big databases using PHPmyadmin.

Ext3
=====
Maximum volume size: 2TB (1KB block) to 16TB (4KB block)
Maximum number of files: number of bytes in volume/2^13.
Maximum file size: 16GB (1KB block) to 2TB (4KB block)

dirk wrote: I never heard about such a limit. If you provider limits the number of files you should change the provider. Sometimes the FTP-Servers display only the first XXXX files.
Then you can use php filemagers like explorer.

It definitely exists. We've come across it on ntfs (32 bit OS) and ext3. It's documented somewhere.

Ext3
=====
Maximum volume size: 2TB (1KB block) to 16TB (4KB block)
Maximum number of files: number of bytes in volume/2^13.
Maximum file size: 16GB (1KB block) to 2TB (4KB block)

[/quote]

It turns out the hosting service places a limit on the number of files. We hit the limit last night :(.

No matter, I tested mysql using MEDIUMBLOB type for the images and it worked fine. So we'll do it that way.

Cheers.

Dirk,
After playing around with the mysql db I concede your strategy of placing images in directories makes sense: there's significant latency pulling 800px jpg images from mysql compared to linking to files on the server.

My hosting services have confirmed file number limits but have lifted it for me.

Cheers

Hi, we manage on our site about 30.000 images with images joodb directory. We meet a list limit problem with FTP to 5.000 files. So we have organized with sub-directories each one containing 1000 images, i.e 2000 files 1000 + 1000 for thumbs (original file is deleted). Each sub-directory is named with 3 left most digit of unique-id (sub-dir R100 contains images 100000 to 100999 and so on ...).

With imported files we are able to manage the image name in the correct sub-directory.

The lasting problem is with uploaded entry because the joodb function load in the root directory. So the new entries are misplaced, and you have to move them to the correct sub-dir and update the image name in the joodb table.

Hi Guygui, we manage on our site about 30.000 images with images joodb directory. We meet a list limit problem with FTP to 5.000 files. So we have organized with sub-directories each one containing 1000 images, i.e 2000 files 1000 + 1000 for thumbs (original file is deleted). Each sub-directory is named with 3 left most digit of unique-id (sub-dir R100 contains images 100000 to 100999 and so on ...).

With imported files we are able to manage the image name in the correct sub-directory.

The lasting problem is with uploaded entry because the joodb function load in the root directory. So the new entries are misplaced, and you have to move them to the correct sub-dir and update the image name in the joodb table. I suppose i have to hack the upload function, because dirk doesnt gave me a solution ;)