Seems installing the new Community Server :: Forums isn’t as ‘isolated’ as its documentation claims…

Ok, so any action you take against your database is your own responsibility… so this is my fault, but I’m still miffed.

I installed the new drop of the Forums code from Rob Howard and co… and one of the various bits of information I picked up from the support forum and the docs was that I could happily install this onto an existing database because (quoting from the readme here)… “All the objects in the Forums product use the forums_ prefix so there shouldn’t be any problem” . Whoops, guess they made a small mistake there, it should have been most of the objects use the forums_ prefix… their sql scripts happily drop any existing table named “Vote”… killing the vote table for my online polls… including all of the votes that had occured since my last export… ouch.

Now, as I said earlier, this is all my fault… I looked at a bit of the sql script and decided to trust the docs… which is a bit silly when it involves my own data… but perhaps learning about my folly will remind you to read any installation sql scripts carefully, even when they’ve been documented as safe…

Seems installing the new Community Server :: Forums isn’t as ‘isolated’ as its documentation claims…

3 Responses

  1. Ouch! Apologies Duncan!

    We’ll be sure this issue is addressed in our next release. Thanks for the heads up, and sorry for the clobbered table.

    Take care,
    -Jason

    Jason Alexander September 1, 2004 at 11:20 am #
  2. Oh man, sorry about that. The Vote table is a hold-over from the Vote Control that we use that was originally released as a stand alone — we’ll get this fixed.

    Rob Howard September 1, 2004 at 11:25 am #
  3. There are also some other objects without the forums prefix … I found this out while moving my webhosts earlier this week. Im actually really talking about the function HasReadPost.

    Matt Hawley September 1, 2004 at 12:02 pm #

Leave a Reply