Well :)
That means I'm gonna have'ta rewrite the search logger pretty much from the ground up :)
The only place multiple primary keys find a use is in logging something that is incremented or modified by something else, such as daily keywords. Basically, a text-based key system. Since the 'autoincrement' function seems to be the basis of Links SQL, in keying tables, using it for something like search logging incurrs only a minor penalty, and most likely -- as you say -- will save a lot of code overhead maintennence headaches.
Essentially, all Links SQL tables should have an AutoIncrement field ID or AutoID as the first field in the table, as both a stylistic and functional process. It would allow the same functions to work on all tables, reguardless.
To this end.... you might want to add to the admin a way to list all the tables in the links database (ie: any table with the current links prefix) and allow a user to create and/or modify a .def file. It should be a simple thing to add, but it will save a lot of support headaches, especially as the number of supported plugins starts to rise.
PUGDOG� Enterprises, Inc.
The best way to contact me is to NOT use Email.
Please leave a PM here.
That means I'm gonna have'ta rewrite the search logger pretty much from the ground up :)
The only place multiple primary keys find a use is in logging something that is incremented or modified by something else, such as daily keywords. Basically, a text-based key system. Since the 'autoincrement' function seems to be the basis of Links SQL, in keying tables, using it for something like search logging incurrs only a minor penalty, and most likely -- as you say -- will save a lot of code overhead maintennence headaches.
Essentially, all Links SQL tables should have an AutoIncrement field ID or AutoID as the first field in the table, as both a stylistic and functional process. It would allow the same functions to work on all tables, reguardless.
To this end.... you might want to add to the admin a way to list all the tables in the links database (ie: any table with the current links prefix) and allow a user to create and/or modify a .def file. It should be a simple thing to add, but it will save a lot of support headaches, especially as the number of supported plugins starts to rise.
PUGDOG� Enterprises, Inc.
The best way to contact me is to NOT use Email.
Please leave a PM here.
