I think, I see how your solution works. Of course your solution works, but is not optimal from the viewpoint of database.
It seems that you create new fields into Links table, but not just for 1 service (as recommended) but for more services. However extending the database this way, is not correct (however works fine), because the result is an unoptimized, unnormalized database. Each service should have a separate table, where only those fields are listed, which belongs to the service.
In optimal case, you should have more Links tables, like Links_Service1, Links_Service2, etc...
I think, the problem is, that the add.cgi doesn't have a database input field, where you could pass your decision, into which database the add.cgi should add those filled input fields.
In my ideal case, I should have 1 Category table, and as much Links_ServiceN tables as much service I have.
Then I could manage more services from one LSQL installation.
Anyway thanks for your suggestion!
You helped me seeing the problem more clear.
I still await more suggestions...
There might be another solution which would fit my needs, but I might missed it until now...
Any more ideas?
Best regards,
Webmaster33
Paid Support from Webmaster33. Expert in Perl programming & Gossamer Threads applications. (click here for prices)
Webmaster33's products (upd.2004.09.26) | Private message | Contact me | Was my post helpful? Donate my help...
It seems that you create new fields into Links table, but not just for 1 service (as recommended) but for more services. However extending the database this way, is not correct (however works fine), because the result is an unoptimized, unnormalized database. Each service should have a separate table, where only those fields are listed, which belongs to the service.
In optimal case, you should have more Links tables, like Links_Service1, Links_Service2, etc...
I think, the problem is, that the add.cgi doesn't have a database input field, where you could pass your decision, into which database the add.cgi should add those filled input fields.
In my ideal case, I should have 1 Category table, and as much Links_ServiceN tables as much service I have.
Then I could manage more services from one LSQL installation.
Anyway thanks for your suggestion!
You helped me seeing the problem more clear.
I still await more suggestions...
There might be another solution which would fit my needs, but I might missed it until now...
Any more ideas?
Best regards,
Webmaster33
Paid Support from Webmaster33. Expert in Perl programming & Gossamer Threads applications. (click here for prices)
Webmaster33's products (upd.2004.09.26) | Private message | Contact me | Was my post helpful? Donate my help...
