Bugs & SQL queries

[OliverJohnson]

Got to be honest and say that I can't see any difference in terms of resolving bugs since I last posted a few days ago. I assume this just means that the developers are simply working their way through a very, very long list of bugs.

Another bug to add to the list if you haven't already noticed is that the site constantly suggests that I need to login or register even though it shows that I am logged into the forum. Looks like some more work needs to be done on bridging of the many databases you appear to be running.

Speaking of databases I couldn't help but notice on the importance of tags you seem to be placing on all areas of this site. You have them in the blogs, in the gallery, in the tutorials, in the reviews and even in forum posts. It's a nice idea but have you actually sat down and thought about the impact this could have on your server?

What I mean is, you apparently have even before the main launch over 100,000 members and if everyone does add tags to any content that they generate and if you guys behind PhotoRadar also continue to make as much use of tags as you are then very, very quickly you are going to have thousands of tags in the database. This is going to have two effects:

1. With everyone able to create tags then they are going to become incredibly subjective and therefore largely pointless for example someone writing something about Lightroom might also use the tag Editing, whilst someone else might use the tag Processing. Without enforcing some kind of restrictions on their use then they are going to become pointless very quickly.

2. If people actually use the tags then aren't you going to create a hell of a lot of SQL queries and if this is only going to get worse if you do have two or three separate databases and as the site grows? End result, the server will grind to a halt under SQL requests.

Originally Posted by OliverJohnson

2. If people actually use the tags then aren't you going to create a hell of a lot of SQL queries and if this is only going to get worse if you do have two or three separate databases and as the site grows? End result, the server will grind to a halt under SQL requests.

Oooo yeah. If the site ever gets launched that could be the thing that kills it. Interesting.