Question Locked

Web-based Application using MySQL as database

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Im developing a web-based application in which my site has three kind of users; Guest, Registered User and Admin. Guest can only access certain contents of the site while both registered users and admin have full access.

As im quite new to MySQL, so im a bit lost (Tho I can use 3rd party program to manipulate the database on the fly). In MySQL, there is a database called, consisting many tables. One of them is which stores infomation who can access that particular database.

My question is:
1) Does every registered User information such as password and user ID must be stored in the table of database or enough to use one ID and password for this group (Since MySQL does support Multi-User connection)

2) What is the best way to store images, video, and Audios? Store as binary object or store the path to the files (its location)?? I ve been reading both pros and cons of the two approaches and now still skeptic which one to choose.

Any suggestion/advice are most welcomed and I truely appreciate it. Thanks in advancw

2 replies

by tony hopkinson

in MySQL, then map the web logins by role is the usual way to do this sort of thing.

You could create a database user for each registered account + guest and admin roles, but you'll get far more options than you want or need.

Usually you just create a registered users table and only assign a token if they are in there.

Images or links

Personally I don't like cluttering a database with data I can't analyse with query, that isn't optimised in terms of storage and is somewhat harder to access outside of writing an application.

Question came upm again recently for us. Eventually ended up popping the images in a table. Big factors were backing up and deployment (client server app). While links would be more efficient in many respects, the increased points of failure far outweighed the minimal gains given the amount of data we were talking about.

This discussion is closed to new replies.