I had just uploaded to

Reece S — Fri, 08 Feb 2008 17:51:32 +0000

I had just uploaded to Drupal, a module that integrates ajaxim into Drupal. I noticed they lack in good Chat services.

No, the main reason I am switching, like you said, because they have something Drupal does not.

No don't get me wrong, I still think Drupal is the best maintained, and easily the best scripted, but for my particular use, e107 would be better.

Cheers for the info.

It has more support, more

JeevesBond — Fri, 08 Feb 2008 10:07:05 +0000

It has more support, more modules, and Less bugs.

Not sure about this. Drupal has ~2,000 modules, e107 has 187 (at time of writing). Don't know about the support and bugs, never really had a problem personally. There are plenty of reasons to not like Drupal, but lack of modules isn't one of them. Maybe it's that Drupal lacked a particular module you wanted that e107 has got? That's fair enough.

Just use whatever you want to use. None of these projects are really competing with each other, they're all Free software, run and maintained by their respective communities. Free software developers usually think a little like this: 'It's cool if my software works for other people, but what's important is that it works for me.'

What happens then is people find the work and discover it works well for them as well as the person whom originally wrote it. They usually find the software lacks some functionality, or has some bug or other. As it almost works for them, they submit a patch to add the functionality or fix the bug. This is how a community grows around a project.

So saying: 'I'm moving to project X, Drupal doesn't do what I need.' Is rather pointless, as it doesn't help the project, or fix any bugs, no-one is going to be interested. Really, just use whatever the heck you like. e107 probably does some stuff that Drupal doesn't, or works in a way that better fits you personally. That's great! Most of all though, I hope you can make a contribution to the e107 community.

Ahh, OK, cheers. I have just

Reece S — Fri, 08 Feb 2008 09:30:46 +0000

Ahh, OK, cheers.
I have just closed my website because Drupal aint right for me. I am going back to e107. It has more support, more modules, and Less bugs.

Cheers for the info. I can still use this code on the new platform.

Thank you to everyone who has helped on this topic.

How could this be initiated

JeevesBond — Fri, 08 Feb 2008 02:08:38 +0000

How could this be initiated on the SQL Server?

It already is. mysql_query() will send the query up to the database server, the database server will process it and return the result to PHP.

You could optimise that code a bit by using a SQL COUNT() instead of the mysql_num_rows() PHP function:

<?php
$chatrooms = mysql_result(mysql_query('SELECT COUNT(*) FROM ajaxim_chats'));
print '<strong>Public chatrooms:</strong><br />'. $chatrooms;

$users_online = mysql_result(mysql_query('SELECT COUNT(*) FROM ajaxim_users WHERE is_online=1'));
print '<strong>Users online:</strong><br />'. $users_online;
?>

mysql_result is a good function to use here as the SQL is only ever going to return one value, no multiple rows or any of that malarkey.

OK... But how would I go

Reece S — Thu, 07 Feb 2008 18:08:40 +0000

OK... But how would I go about this?

This is my current PHP code:

<?php
$result = mysql_query("SELECT * FROM ajaxim_chats");
$num_rows = mysql_num_rows($result);
echo "<strong>Public Chatrooms:</strong><br />$num_rows\n";
?>

<?php
$result = mysql_query("SELECT * FROM ajaxim_users WHERE is_online = 1");
$num_rows = mysql_num_rows($result);
echo "<strong>Users Online:</strong><br />$num_rows\n";
?>

How could this be initiated on the SQL Server?

Thanks in Advance.

I am currently making all

JeevesBond — Thu, 07 Feb 2008 02:21:05 +0000

I am currently making all the queries from PHP, what significant difference would there be if I let the database do all the work?

Greg K is saying that the general rule is to make the database do as much of the hard work as possible. Writing the SQL in PHP and running the query using mysql_query() is the right way to do this, that's not the hard part.

Where a lot of programmers go wrong is to do a basic SQL query, then loop through the results using an if statement to get the records they want. It's usually wrong to use an if statement instead of a WHERE clause in your SQL.

Yeah, thats true I am

Reece S — Wed, 06 Feb 2008 17:11:43 +0000

Yeah, thats true

I am currently making all the queries from PHP, what significant difference would there be if I let the database do all the work?

All questions are worth

Greg K — Wed, 06 Feb 2008 16:55:54 +0000

All questions are worth asking. Never delete a question even if you find the answer, instead post a second message saying you solved it, and let people know how you solved it.

This serves two purposes. 1. Sometimes you may find something that works, but someone else knows a more efficient way of doing it. 2. Someone else may encounter the same issue and do a search and find your post, and then solve their problem too.

-Greg

Concidence. I had just

Reece S — Wed, 06 Feb 2008 16:46:48 +0000

Concidence. I had just figured that out right now. I was just returning to TWF to delete this post. Thanks Teammatt3.

Yeah, our codes are identical. Except I went with

<?php
\"SELECT * FROM User WHERE is_online = 1\"
?>

instead.

Thanks for your help, and sorry for wastin anyones time (again).

It seems to me, that I try to do something, then after a few days, I give up, and post on TWF, then guaranteed, I will figure it out when I have already posted the darn question!!!

Cheers anyways.

teammatt3 wrote: I heard

Greg K — Wed, 06 Feb 2008 16:43:35 +0000

teammatt3 wrote: I heard it's faster to make MySQL do your counting.

It is a good general rule to have the DB server do as much calculating and figuring as possible and then pass back the final results to the "client" (in this case, PHP)

This is even more so when you have a separate DB server (physical box) from the web server. There is less recourses to passing back and forth, and if done right, the SQL server should be fine tuned for the DB server, so should calculate faster than on a "general" server set up fro multiple operations.

But as you are already have a query else where (to possible list the online users), the format you have is correct with the mentioned addition of the WHERE clause.

-Greg