#13 table restructuring and SQL queries

[dyinman]

Below is a copy of a post I've already made in another
location dedicated to this application:
--------
After talking a bit with dragon about the structure of SS
as it stands now, here's a couple of suggestions:

1) Restructure your tables. If you let the database do
the work for you, you can make it much easier to
implement into other frontends... and it'll save you a fair
share of coding. It would merely be adding another
constraint to your query instead.
On top of being easier to implement on other front ends
(web, java applets, C++ applications, etc), it'll be much
more organized as well.
Furthermore, if you do this, others who want to use
what you've done will have an easier time in doing so.
They should then only have to configure but a few
options, and be good to go straight from the download.

2) If you do a makeover on your tables, you can make
a .txt file (or whatever type is required) that includes a
list of SQL queries that will create a template database
for anyone else who decides they want to use SS. A
good example of this would be PHPNuke. It would take
a good long while to create all the tables needed, but
they have a template query file for you to create the
tables already.
Even though SS is considerably smaller, it would still be
a good idea.

I think it'd be a good thing to sit down, think over what
kind of database you would want to use, think about the
relationships and how you can use that to your
advantage in your programming, and re-design this
mother.

Let me know what you think of my suggestions and if I
may be of any help.

Good luck finishing this sucker up!

-dyinman

[Bryan Burgers]

Logged In: YES
user_id=898425

Alright, I do like this idea. However, I feel that since
the searches CAN still be performed without this entry in
the database, it isn't high on my priority list. when i
revist the mysql writer module, i'll definitely look into
this though.