Peter J. Boettcher — Thu, 20 Apr 2000 12:59:00 +0000

Randall,

Great work!

Regards,
Peter J. Boettcher

Randall — Thu, 20 Apr 2000 03:03:00 +0000

Hey, I have finished my mysql driven forum. I am still adding features though. Check it out My forum

------------------
Visit the dLo.Network
http://dlo.net

Peter J. Boettcher — Mon, 17 Apr 2000 13:43:00 +0000

Patrick,

I guess the only thing that might speed things up a little bit would be to have a stored procedure that would be called by a trigger or rule.

Regards,
Peter J. Boettcher

anti — Mon, 17 Apr 2000 09:15:00 +0000

Hi,

I've been gone for a while, so fogive me for my late answer.

The way to go is letting the database to what it was designed for and you doing your part of the job.

Some time ago I worked on an internal database that hat over half a billion entries in one table and the response time was much lower than one second.

What do you think you will gain by splitting your tables ?
A good database does this (based on your keys) anyway. And it does that much faster than you can ever do it in Perl/PHP/Rexx/etc.

Just save yourself the time (and headache) and use it to read a good database modeller book. No, not "SQL for Dummies" or "Access in 21 Days". Get something real.

just my $.02

ciao
Anti
ps:
Everybody seems to be writing his own (database driven) board software, but boardzilla seems to be starving ... just wondering...

Patrick Davis — Mon, 17 Apr 2000 00:54:00 +0000

No, I mean on the server side, the the column is in the servers memory and can be parsed faster

------------------
OMG It's Furious George!!!

Peter J. Boettcher — Sat, 15 Apr 2000 01:38:00 +0000

Patrick,

Three letters, XML !

What you describe is one of the benefits of XML/XSL. Pulling selected records out of a database, holding them in XML and letting the user manipulate that data without going back to the server.

You could also do this by storing the records in a client side (JavaScript) array, by using ASP to write the values into the JavaScript.

Unfortunately, both these methods require at least an intermediate level of programming knowledge, and both would be quite a project to do, and currently XML support by the browsers isn't there yet.

Acutally, using ASP you could probably store something using the application object. Since this object is shared by all users on your website this could work. I'll have to think on this one!

Regards,
Peter J. Boettcher

Patrick Davis — Fri, 14 Apr 2000 22:47:00 +0000

I know you don't have to specify secondary keys, but is there a way to make columns you query often resident in memory, or something to that effect?

------------------
Open Source is the future!

Peter J. Boettcher — Fri, 14 Apr 2000 18:03:00 +0000

Patrick,

I'm not sure what you mean. Do you mean if you have to declare secondary keys when you make your statement?

Sorry, but I'm really not sure what you mean.

Regards,
Peter J. Boettcher

Patrick Davis — Thu, 13 Apr 2000 22:15:00 +0000

Is it necessarry to specify queried columns in a table? Like say there is a feild named ID, as the Primary Key. How about secondary keys, do you define those when creating a database?

------------------
Open Source is the future!

Ralph Slate — Thu, 13 Apr 2000 20:25:00 +0000

I'm not sure we're talking about the same thing. When I say "indexes", I mean the physical database index that is updated always -- I don't mean a separate "index table" that might have things like thread subjects in it.

Physical indexes are always maintained by the database, and require no manual updates. You may want to rebuild them from time to time to make sure they are stored efficiently -- physical order matters in most databases.

The only caveat on indexing is that 1) indexes take disk space, and 2) they slow down insert operations because an insert needs to not only insert in the table, but must also insert into the indexes.

Ralph
http://www.hockeydb.com