[]
Dave_L said:Thanks.
I suggest adding another table:
CREATE TABLE w3t_Mods_Files (
M_ID int(11) NOT NULL default 0,
M_File varchar(255) NOT NULL default '',
M_New char(1) NOT NULL default '0',
KEY M_ID (M_ID),
KEY M_File (M_File)
);
This table keeps track of which files were added (M_New = '1') or modified (M_New = '0') by each mod.
Each row of the table contains one filename, so if a mod affected ten files, then there would be ten rows.
Then by doing the appropriate query, you could obtain a list of all files related to a specific mod, or a list of all mods that affect a specific file. [/]
Thanks for the suggestion. I was thinking about something towards that direction, but wasn't sure exactly how to approach it yet.
Ultimately an interesting idea would be to come up with some kind of standard SQL string that every mod'er could supply (like the standard format that people use for posting mods), then it could be integrated with the forums here, and at the same time the same SQL query could be run by those who install it into their .threads, provided they have the mod first.
Basically:
-author writes mod, submits it on a form here similar to the admin/ubbtedit_modification.php form, except it also generates a post using the newpost.php (so that file upload is same as always)
-the form is shown in the parent post, and has a pop-up link with generated SQL code to update the modification table when the code is installed
-admin-user of the code makes the hacks as usual, and runs the SQL query to update their modifications table
I hope that's not too big looking, but that's what I think a version one would be like. I've written something similar in a private hack that was like photopost, minus the generated SQL code of course
