I was planning to set up a website for a bunch of ebooks that displays each ebook images, descriptions, and download links in a row. I know that doing it in php with mysql is the best way to go. But I've been tormentedly figuring out how should it be done. I would greatly appreciate any words from you guys. Thanks! \m/

do you want to store images in mysql database. or store them in files and just store the link in the database?

@Paul & Maria2009

You can do it pretty easily if you signup for free webhosting. Bear in mind, the freehost will require at minimum: 1 free mysql database. Once you have that, and by the way if you pay for hosting that should be part of your package, and you will likely have access to more than one mysql database as well.

Once you have that, you log into the servers control panel, and you will see a link to the Mysql section. From there it's all yours. It will take some time to learn, but that's where you will NEED to learn this stuff from.

Hth,
-Brian

It is always the good practice not to store images to the database. Because as the more rows are getting added to the database, your database server performance will go down. Hence, you should store the images on the file system and just save the link to the image in the database.

All popular application saves the attachments this way, The best example is Kayako helpdesk software.

Originally Posted by twhdir

It is always the good practice not to store images to the database. Because as the more rows are getting added to the database, your database server performance will go down. Hence, you should store the images on the file system and just save the link to the image in the database.

All popular application saves the attachments this way, The best example is Kayako helpdesk software.

but on the other hand, storing images in files then just storing the links in database can be troublesome when transferring website. because you need to keep up file structure the same. mostly at each move there are always some bugs that comes up either with lost files or deformed files structure due to different file system or whatever.
other trouble, is files permissions. you need to set them probably or images will not be created or deleted or even will not be accessed.

in short, if images are just few thousands it is better to have them up in the database to avoid the kinks comes up with file system

Originally Posted by twhdir

It is always the good practice not to store images to the database. Because as the more rows are getting added to the database, your database server performance will go down. Hence, you should store the images on the file system and just save the link to the image in the database.

All popular application saves the attachments this way, The best example is Kayako helpdesk software.

No, it should not....
If you design your db well enough, it sure will take some milliseconds more, but the "performances" won't degrade.

Beside, saying that pictures should always be stored outside a db is just a myth, and can be misleading.
I have programmed a web service that takes screenshots of web pages, and I do not store them as files.
I store them in a postgresql DB and in a memcached server instance.

Why !?
Because the db adds only a minor overhead, if no overhead at all. Mind you, the filesystem management is an overhead too...
Because I can have several server working together, and having files shared between them is just like sleeping under an anvil, something is bound to happen. Be it name conflict, locking error or network problems.

So, storing files in a DB can be a well more suitable way to handle them than a filesystem only one.

But as for the OP question, it's true that storing the pics in the DB would be overkill.
But if your question still torment you, there is a good article there: http://www.phpriot.com/articles/images-in-mysql

Life is too short to be serious, laugh it up.



gratuit pour mobile sonnerie portable mp3 - Sonnerie portable MP3 est en effet un pouvoir de l'innovation technologique. Êtes-vous familier avec cette sonnerie portable?gratuit pour mobile sonnerie portable mp3

At least 8 times a day !

it is not a good idea, it will make you database extend rapidly!

So what !?
Why would it be a problem ?
Either you make your db grow, or you fill your hdd, so what's the difference ?

Clean up your db, remove old, unused data, prevent duplication, and it won't be a matter.