PHP/MySQL article database

nomadiconion

I want to program a web page to show articles that someone uploads. Is it efficient to store the articles on a MySQL database and query them?

Cheers!
Julian

bradgrafelman

Well, MySQL is a database server, and the definition of "database" according to Google is "A structured set of data held in a computer, esp. one that is accessible in various ways." So are the pieces of an article a "structure set of data" that you would like to be "accessible in various ways" ? 😉

I'm going to make some wild guesses/assumptions about your knowledge/skill level (in regards to PHP+MySQL) and say that what would really be efficient for you to do is use an existing CMS like WordPress to do this for you.

nomadiconion

bradgrafelman;11013447 wrote:
Well, MySQL is a database server, and the definition of "database" according to Google is "A structured set of data held in a computer, esp. one that is accessible in various ways." So are the pieces of an article a "structure set of data" that you would like to be "accessible in various ways" ? 😉

I'm going to make some wild guesses/assumptions about your knowledge/skill level (in regards to PHP+MySQL) and say that what would really be efficient for you to do is use an existing CMS like WordPress to do this for you.

THanks for the reply. The webpage is already running but the articles are writen directly on the page one under the other and you have to scroll down infinetely to go to the bottom of the page. Can I put wordpress inside this already built webpage? What other suggestions do you have?

rltamm

nomadiconion;11013453 wrote:
THanks for the reply. The webpage is already running but the articles are writen directly on the page one under the other and you have to scroll down infinetely to go to the bottom of the page. Can I put wordpress inside this already built webpage? What other suggestions do you have?

you can condense the page by using a easy javascript to condense the articles and lick to drop the article down...

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<title>Untitled Document</title>
<script type="text/javascript">
	document.cestatus = 0;
	function cecontrol(id){
		if(document.cestatus == 0){
			document.getElementById(id).style.display = "block";
			document.cestatus = 1;
		}else{
			document.getElementById(id).style.display = "none";
			document.cestatus = 0;
		}
	}
	cecontrol("row");
</script>
<style type="text/css">
	#row{display:none;}
</style>
</head>

<body>
<button onclick="cecontrol('row')">-/+</button>
<table id="row" >
	<tr >
		<td>Data</td>
		<td>Data</td>
	</tr>
	<tr >
		<td>Data</td>
		<td>Data</td>
	</tr>
</table>
</body>
</html>

rltamm

wasntreally a php code just used to using the tags.. lol... just create a new page using whatever program your using.. copy entire script into page.. and save... you'll see a button to expand or collapse the "article" just copy into field and replicate... simple and will condense you page considerably

nomadiconion

Thank you very much for that rltam. What would you suggest to be the best way to store the articles?

CHeers!

rltamm

it depends. the script i gave has you just place it on the page. playing a little you could probably make each into an small php file and access each with an "include" then create a folder and add each in it, a php with txt will be very small so you wouldn't need a ton of space.

Creating a form could work and it can function to store each on submission to your Database but this route is a lot more technical, you would have to create the DB tables, the script to send and receive the information, and keep it condensed ... this is not my area and I wouldn't be able to assist.

But I am sure it is possible... honestly I think it would be easy enough to just save them as individual php files and run with it. ...<this route.. you would need less script and a simpler to edit in my opinion.

nomadiconion

rltamm;11014093 wrote:
it depends. the script i gave has you just place it on the page. playing a little you could probably make each into an small php file and access each with an "include" then create a folder and add each in it, a php with txt will be very small so you wouldn't need a ton of space.

Creating a form could work and it can function to store each on submission to your Database but this route is a lot more technical, you would have to create the DB tables, the script to send and receive the information, and keep it condensed ... this is not my area and I wouldn't be able to assist.

But I am sure it is possible... honestly I think it would be easy enough to just save them as individual php files and run with it. ...<this route.. you would need less script and a simpler to edit in my opinion.

Thanks for that... I'm gonna give the DB a try because I want the writers to submit the articles from a link i'm gonna give them.
If i go with the php separately, do i have to edit the "include" everytime the user adds a new article?

CHeers!

rltamm

nomadiconion;11014095 wrote:
Thanks for that... I'm gonna give the DB a try because I want the writers to submit the articles from a link i'm gonna give them.
If i go with the php separately, do i have to edit the "include" everytime the user adds a new article?

CHeers!

it would work all together different... the "include" i was referring to would put the included php article in the collapsible table... each table header would say the article and the include would go into the data field to show the article into that field on your page.

if the articles are submitted via form to the database you would need a script to add it to the page for viewing I would guess.. but like i said actual database work/scripts is not my cup of tea.. someone else would have to assist you there.

cretaceous

you'd be mad to do it as lots of little text files - use a database
It may be more work up front but in the long run you'll thank yourself