Can you really store a picture file (.digital, .presen, etc) in MYSQL database? Or get it done just stores in system and takes reference path of image?

I'm using ASP.Internet C#, if you have sample code, it is always good should you could share it.

Yes, you are able to store image files (and then any other files) inside a database as binary data.

In MySQL, the [cde] data type may be used to make this happen.

A BLOB is really a binary large object that may hold a flexible quantity of data. The 4 BLOB types are TINYBLOB, BLOB, MEDIUMBLOB, and LONGBLOB. These differ only within the maximum entire values they are able to hold. [...]

BLOB values are treated as binary strings (byte strings). They've no character set, and sorting and comparison derive from the number values from the bytes in column values.

To begin here a publish that is pretty much like that one: Should I store my images in the database or folders?

Next an example for storing images into database: http://www.dotnetcurry.com/ShowArticle.aspx?ID=129&AspxAutoDetectCookieSupport=1

For me it is dependent whether you decide to store images inside your database or perhaps in folders. Both techniques have there benefits and drawbacks.

Here a brief comment from asp.internet forums:

In The Event You Really Store Images within the Database?

About 10 years ago, I began among the very first Internet projects—an image data bank. I was designed to deliver images of numerous dimensions and resolution to registered customers. Each image was designed as an accumulation of images, in the thumbnail towards the greatest resolution. The biggest image available involved 4 Megabytes. Each image saved within the archive required up an overall total of 6 Megabytes of space.

The rear-finish database wasn't running on the Microsoft platform but provided support for BLOB fields. With little debate, we made the decision to keep explanations along with other catalog information within the database and also to store images as individual files under a properly-known path. We saved in the database enough information for the program to retrieve the file. Being created for a comparatively small quantity of registered customers, the application never demonstrated scalability problems and never did anybody on they, or any customers, complain about performance.

Can this brief experience—especially an event from the relatively old chronilogical age of software and database technologies—be used to illustrate the brilliance of file-based storage over database storage? Definitely not, but reading through between your lines of methods modern DBMS systems implement BLOB fields, I have used this experience to formulate a concept about image storage and databases.

In a nutshell, in the event you consider storing images inside a database? If you want to edit the pictures frequently, I would recommend storing the pictures separate files around the server's hard disk. When the size the pictures are extremely large (for example, 100s of mb), I suggest storing the pictures separate files within the file system. In case your images are basically read-only and relatively static, and when you measure the dimensions in kilobytes, you are able to consider storing your images within the database.

You need to produce a byte array in the image and store that within the database.

BLOB

To transform the information to a picture:

public static byte[] ConvertImageToByteArray(Image imageIn)
{
    var ms = new MemoryStream();
    imageIn.Save(ms, ImageFormat.Png);
    return ms.ToArray();
}

4GuysFromRolla.com comes with an article about this which i used as reference after i was writing code to keep binary data directly inside a database: http://www.4guysfromrolla.com/articles/120606-1.aspx

Personally I've found so that it is much less trouble to keep the look within the filesystem along with a pointer within the database.

Take this... ASP.NET Image uploading with Resizing You'll find number of good examples.