I've been doing a lot of stuff with SQL lately and was thinking about porting over parts of Links 2.0 to SQL.
First thing I'm working on is to make a search script for links. There was (briefly) an SQL search mod available several years ago for Links 1.x. I'm working on recreating that. So far I've written a routine that goes through your links.def file and creates your table based on %db_def, and then a routine that loads links.db into the new table. I already have a search script for my own SQL directory system that I wrote last year, so I can easily change this to work with Links. The search script allows for fulltext index as well as boolean searches. Per field searches can be added later on if anyone needs that.
The search plugin will require and extra step during a build. You'll need to run a script to wipe out the links table and reimport whenever you make changes to your database.
The second thing I'm working on is an SQL version of PortalLinks. This version will require the search plugin to function. This allows for quicker access, and sorting of saved favorites. (There is also I an version that runs off of links.db, but it isn't as flexible or fast, not did I ever really release it.)
Before anyone asks, NO I will not rewrite Links 2.0 to be fully SQL. It's not that it's difficult (it's not), it's because it would take forever, it's a waste of time, and I don't think Alex would approve of it anyway.
--Philip
Links 2.0 moderator
First thing I'm working on is to make a search script for links. There was (briefly) an SQL search mod available several years ago for Links 1.x. I'm working on recreating that. So far I've written a routine that goes through your links.def file and creates your table based on %db_def, and then a routine that loads links.db into the new table. I already have a search script for my own SQL directory system that I wrote last year, so I can easily change this to work with Links. The search script allows for fulltext index as well as boolean searches. Per field searches can be added later on if anyone needs that.
The search plugin will require and extra step during a build. You'll need to run a script to wipe out the links table and reimport whenever you make changes to your database.
The second thing I'm working on is an SQL version of PortalLinks. This version will require the search plugin to function. This allows for quicker access, and sorting of saved favorites. (There is also I an version that runs off of links.db, but it isn't as flexible or fast, not did I ever really release it.)
Before anyone asks, NO I will not rewrite Links 2.0 to be fully SQL. It's not that it's difficult (it's not), it's because it would take forever, it's a waste of time, and I don't think Alex would approve of it anyway.
--Philip
Links 2.0 moderator