Hello all.
I'm currently using Links 2.0 as a news database. It has been fairly heavily modified and tinkered with so that it now does exactly what I need it to do, as an integrated part of a much larger web site. None of the static pages generated are accessible on their own, only through php and ssi includes.
At any rate, as the database grows, I anticipate quickly needing to upgrade from the flatfile system, as each record is pretty large (maybe 10-15K each, many with multiple pages worth of html formatted text), and I just imagine that Links 2.0 won't be able to handle too many of those before getting into trouble...
Links SQL would be the obvious choice, but I have some concerns about the ease of the upgrade process. I mean, I'm sure it's pretty easy to transfer the database itself, but I suspect the structuring and formating work I've done would have to be completely redesigned, which could be somewhere between a major and an enormous pain.
Has anyone had any experience with this kind of problem before? Since I don't really have any idea how LinksSQL works, it's hard to predict what sorts of difficulties I might have.
One potentially silly question (but it never hurts to ask, right?): would it be possible/make sense to modify Links2.0 to work with a MySQL database without making the full upgrade to LinksSQL?
Just putting this out there in case anyone has advice.
Thanks in advance.
Best regards,
adamuforestasan
Fractured Atlas :: Liberate the Artist
Services: Healthcare, Fiscal Sponsorship, Marketing, Education, The Emerging Artists Fund
I'm currently using Links 2.0 as a news database. It has been fairly heavily modified and tinkered with so that it now does exactly what I need it to do, as an integrated part of a much larger web site. None of the static pages generated are accessible on their own, only through php and ssi includes.
At any rate, as the database grows, I anticipate quickly needing to upgrade from the flatfile system, as each record is pretty large (maybe 10-15K each, many with multiple pages worth of html formatted text), and I just imagine that Links 2.0 won't be able to handle too many of those before getting into trouble...
Links SQL would be the obvious choice, but I have some concerns about the ease of the upgrade process. I mean, I'm sure it's pretty easy to transfer the database itself, but I suspect the structuring and formating work I've done would have to be completely redesigned, which could be somewhere between a major and an enormous pain.
Has anyone had any experience with this kind of problem before? Since I don't really have any idea how LinksSQL works, it's hard to predict what sorts of difficulties I might have.
One potentially silly question (but it never hurts to ask, right?): would it be possible/make sense to modify Links2.0 to work with a MySQL database without making the full upgrade to LinksSQL?
Just putting this out there in case anyone has advice.
Thanks in advance.
Best regards,
adamuforestasan
Fractured Atlas :: Liberate the Artist
Services: Healthcare, Fiscal Sponsorship, Marketing, Education, The Emerging Artists Fund
Upgrading and flexibility